| 2.1 | Approval of the agenda | |
|---|---|---|
| R2-2400001 | Agenda for RAN2#125 | Chair |
| R2-2401539 | Agenda for RAN2#125 | Chair |
| 2.2 | Approval of the report of the previous meeting | |
| R2-2400002 | RAN2#124 Meeting Report | MCC |
| 2.5 | Others | |
| R2-2400003 | RAN2 Handbook | MCC |
| R2-2401855 | (reserved) | nn |
| R2-2401991 | Correction on RACH Optimisation | R3 (Huawei, Deutsche Telekom, China Unicom) |
| R2-2401992 | Correction on TS 38300 for UAV | R3 (ZTE, China Telecom, China Unicom, CATT) |
| R2-2401993 | Corrections of Slrelay | R3 (Huawei) |
| R2-2401994 | Correction on MDT enhancements to support NPN | R3 (ZTE) |
| R2-2401995 | Resource handling for Alternative S-NSSAIs | R3 (Ericsson, Deutsche Telekom, ZTE) |
| R2-2401996 | Correction to 37.340 for CPAC of SON feature | R3 (CATT, Nokia, Nokia Shanghai Bell, ZTE) |
| R2-2401997 | Correction of network timing synchronization status monitoring | R3 (Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Qualcomm) |
| R2-2401998 | Introduction of separate uplink and downlink PDU set QoS parameters | R3 (ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Inc., Samsung, Xiaomi, China Telecom, CMCC, Huawei, CATT, LG Electronics) |
| R2-2401999 | Correction of UL large size SDT data | R3 (Nokia, Nokia Shanghai Bell, CATT, Huawei, ZTE, Qualcomm Incorporated, Google) |
| R2-2402000 | Add a new tigger condition for MT-SDT in TS38.300 | R3 (ZTE, China Telecom, Ericsson, Huawei, Nokia, Nokia Shanghai Bell) |
| R2-2402001 | Correction on 37.340 for stage-2 description of QoE in NR-DC | R3 (ZTE, China Telecom, Ericsson, Huawei) |
| R2-2402002 | Correction of Redcap RAN Paging Request | R3 (Nokia, Nokia Shanghai Bell, Ericsson, CATT, Qualcomm Incorporated, Xiaomi, Huawei, ZTE, China Telecom) |
| R2-2402003 | Support intra-SN subsequent CPAC in MN format | R3 (ZTE, Ericsson, Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, CMCC, LG Electronics) |
| R2-2402004 | Correction of timer-based conditional handover for IoT NTN | R3 (Huawei, Nokia, Nokia Shanghai Bell) |
| R2-2402005 | Correction of timer-based conditional handover for NR NTN | R3 (Huawei, Nokia, Nokia Shanghai Bell) |
| R2-2402006 | Correction on MRO | R3 (Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, CATT) |
| R2-2402007 | Correction for SPR optimizations | R3 (CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Lenovo) |
| R2-2402008 | Introduction of new SPID value for 2RX XR UE [2Rx_XR_Device] | R3 (Nokia, Nokia Shanghai Bell, ZTE, Apple, Ericsson, Qualcomm, Deutsche Telekom, Vodafone, CATT, CMCC, China Telecom, Huawei) |
| R2-2402009 | Stage 2 correction for NR-U | R3 (Ericsson, Qualcomm Incorporated, Deutsche Telekom, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Huawei, CATT) |
| R2-2402010 | Completion of the stage-2 description of S-CPAC | R3 (Nokia, Nokia Shanghai Bell, ZTE, CATT, Huawei, Ericsson, LG Electronics, Lenovo, Samsung, NEC) |
| R2-2402011 | Handover Cancel in CHO with SCG(s) | R3 (Samsung, LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell) |
| R2-2402012 | Corrections on stage 2 descriptions for SON | R3 (Lenovo, Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Samsung) |
| R2-2402013 | Corrections on AI for RAN stage 2 | R3 (Lenovo, Huawei, Ericsson, ZTE, InterDigital, NEC, CATT, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Deutsche Telekom, Samsung) |
| R2-2402014 | Transfer PDU Set Information during data forwarding for Xn handover | R3 (ZTE, CATT, Nokia, Nokia Shanghai Bell, Ericsson, Xiaomi, Qualcomm Inc., CMCC, NEC, Huawei) |
| R2-2402015 | Support of mixed PDUs handling in Non-Homogeneous deployment | R3 (Xiaomi, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Inc., Huawei) |
| R2-2402016 | Correction on ECN marking for L4S and data forwarding | R3 (Huawei, Lenovo, CMCC, Deutsche Telekom, CATT, Nokia, Nokia Shanghai Bell, Ericsson, ZTE) |
| R2-2402017 | Corrections on R18 QoE enhancements | R3 (China Unicom, Huawei, ZTE, Xiaomi, Ericsson) |
| R2-2402018 | Correction to 37.320 on the user consent for trace reporting | R3 (Huawei, CMCC, Ericsson, Interdigtal, ZTE, Nokia, Nokia Shanghai Bell) |
| R2-2402019 | Support of NR Positioning Enhancements | R3 (Nokia, Nokia Shanghai Bell, CATT, Huawei, Ericsson, Xiaomi, ZTE, Samsung) |
| R2-2402020 | Introduction of new SPID value for 2RX XR UE [2Rx_XR_Device] | R3 (Nokia, Nokia Shanghai Bell, ZTE, Apple, Ericsson, Qualcomm, Deutsche Telekom, Vodafone, CATT, CMCC, China Telecom, Huawei) |
| R2-2402021 | Correction of timer-based conditional handover for NR NTN | R3 (Huawei, Nokia, Nokia Shanghai Bell) |
| R2-2402022 | Corrections on R18 QoE enhancements | R3 (China Unicom, Huawei, ZTE, Xiaomi, Ericsson) |
| R2-2402023 | Correction on 37.340 for stage-2 description of QoE in NR-DC | ZTE, China Telecom, Ericsson, Huawei |
| R2-2402066 | Correction on TS 38300 for UAV | R3 (ZTE, China Telecom, China Unicom, CATT) |
| R2-2402067 | Correction to 37.340 for CPAC of SON feature | R3 (CATT, Nokia, Nokia Shanghai Bell, ZTE) |
| R2-2402068 | Introduction of new SPID value for 2RX XR UE [2Rx_XR_Device] | R3 (Nokia, Nokia Shanghai Bell, ZTE, Apple, Ericsson, Qualcomm, Deutsche Telekom, Vodafone, CATT, CMCC, China Telecom, Huawei) |
| 3 | Incoming liaisons | |
| R2-2400010 | LS on draft-ietf-tsvwg-ecn-encap-guidelines and draft-ietf-tsvwg-rfc6040updateshim (Liaison_from_IETF_21Dec2023; contact: Huawei) | IETF Transport and Services Working Group (TSVWG) |
| R2-2400017 | LS on Introduction of NR support for dedicated spectrum less than 5MHz for FR1 to TS 38.300 (R1-2312458; contact: Nokia) | RAN1 |
| R2-2400093 | LS on the progress update of AI/ML Management specifications in SA5 (S5-238107; contact: NEC, Intel) | SA5 |
| R2-2401286 | Way forward on the LS reply to SA5 on AIML | Ericsson |
| R2-2401799 | Reply LS on the progress update of AI/ML Management specifications in SA5 (R3-241183; contact: ZTE) | RAN3 |
| R2-2401820 | LS Reply to SA5 on LS on new definitions of energy efficiency and energy consumption (S2- 2403444; contact: OPPO) | SA2 |
| R2-2401822 | LS on per UE energy consumption in RAN (S2-2403733; contact: Vodafone) | SA2 |
| R2-2401824 | Clarification on the requirements for NTZ (S2-2403859; contact: LGE) | SA2 |
| 4.1 | EUTRA corrections Rel-17 and earlier | |
| R2-2400092 | Reply LS on user consent for SON/MDT for NB-IoT UEs (S5-238102; contact: Ericsson) | SA5 |
| R2-2401196 | Discussion on UE location in RLF report for NB-IoT | Qualcomm Incorporated |
| R2-2401201 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401215 | Mirror CR - Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401219 | Further clarification to PUCCH-ConfigDedicated | MediaTek Inc. |
| R2-2401222 | Mirror CR - Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401273 | Discussion on MFBI | Huawei, HiSilicon |
| R2-2401743 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401744 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401745 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401746 | UE Capability on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401747 | UE Capability on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401748 | UE Capability on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401846 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401847 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401848 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401849 | UE Capability on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401850 | UE Capability on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401851 | UE Capability on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401886 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401887 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| R2-2401891 | Correction on UE location information in NB-IoT RLF report | Qualcomm Incorporated |
| 4.1.1 | Other | |
| R2-2400651 | Correction on Event A3 and A5 for LTE CHO | Huawei, HiSilicon |
| R2-2400652 | Correction on Event A3 and A5 for LTE CHO | Huawei, HiSilicon |
| R2-2400653 | Correction on Event A3 and A5 for LTE CHO | Huawei, HiSilicon |
| R2-2401749 | Correction on Event A3, A4 and A5 for LTE CHO | Huawei, HiSilicon |
| 4.2 | NB-IoT and eMTC support for NTN Rel-17 | |
| R2-2401224 | Correction on reception of SIB32 | ZTE Corporation, Sanechips |
| 5.1.1 | Stage 2 and Organisational | |
| R2-2401806 | Reply LS on combination of HST and RRM relaxation (R4-2403532; contact: Apple) | RAN4 |
| 5.1.2.1 | MAC | |
| R2-2401406 | Clarification of enhanced uplink skipping and CG-UCI R16 | Ericsson |
| R2-2401407 | Clarification of enhanced uplink skipping and CG-UCI R17 | Ericsson |
| R2-2401408 | Clarification of enhanced uplink skipping and CG-UCI R18 | Ericsson |
| 5.1.3.1 | NR RRC | |
| R2-2400654 | Discussion on UE behaviours on neighbour cell measurements | Huawei, HiSilicon |
| R2-2401375 | Correction on when multiple configured grants are signalled | Ericsson |
| R2-2401376 | Correction on when multiple configured grants are signalled | Ericsson |
| R2-2401377 | Correction on when multiple configured grants are signalled | Ericsson |
| R2-2401430 | Correction on reducedCCsDL and reducedCCsUL in overheating report | ZTE Corporation |
| R2-2401431 | Correction on reducedCCsDL and reducedCCsUL in overheating report | ZTE Corporation |
| R2-2401432 | Correction on reducedCCsDL and reducedCCsUL in overheating report | ZTE Corporation |
| R2-2401750 | Correction on reducedCCsDL and reducedCCsUL in overheating report | ZTE Corporation |
| R2-2401751 | Correction on reducedCCsDL and reducedCCsUL in overheating report | ZTE Corporation |
| R2-2401752 | Correction on reducedCCsDL and reducedCCsUL in overheating report | ZTE Corporation |
| R2-2401982 | Miscellaneous non-controversial corrections Set XXI | Ericsson |
| R2-2401983 | Miscellaneous non-controversial corrections Set XXI | Ericsson |
| R2-2401984 | Miscellaneous non-controversial corrections Set XXI | Ericsson |
| 5.1.3.2 | UE capabilities | |
| R2-2400348 | Correction on prerequisite feature for csi-ReportingCrossPUCCH-Grp-r16 | Qualcomm Incorporated |
| R2-2400349 | Correction on prerequisite feature for csi-ReportingCrossPUCCH-Grp-r16 | Qualcomm Incorporated |
| R2-2400350 | Correction on prerequisite feature for csi-ReportingCrossPUCCH-Grp-r16 | Qualcomm Incorporated |
| R2-2400718 | Discussion on UE capability segmentation | Huawei, HiSilicon |
| R2-2400727 | Clarification on ca-ParametersNRDC capability (Understanding#2) | Huawei, HiSilicon |
| R2-2400728 | Clarification on ca-ParametersNRDC capability (Understanding#2) | Huawei, HiSilicon |
| R2-2400729 | Clarification on ca-ParametersNRDC capability (Understanding#2) | Huawei, HiSilicon |
| R2-2400730 | Clarification on ca-ParametersNRDC capability (Understanding#2) | Huawei, HiSilicon |
| R2-2400862 | On the applicability of asyncIntraBandENDC to intra-band NE-DC | Nokia, Nokia Shanghai Bell |
| R2-2401021 | Clarification on the Supported Bandwidth of the SRS-only Cell | ZTE Corporation, Sanechips |
| R2-2401022 | Clarification on the Parallel Tx Capability(r15) | ZTE Corporation, Sanechips |
| R2-2401023 | Clarification on the Parallel Tx Capability(r16) | ZTE Corporation, Sanechips |
| R2-2401024 | Clarification on the Parallel Tx Capability(r17) | ZTE Corporation, Sanechips |
| R2-2401025 | Clarification on the Parallel Tx Capability(r18) | ZTE Corporation, Sanechips |
| R2-2401289 | Discussion on UE capability asyncIntraBandENDC | Apple |
| R2-2401290 | Update on UE capability AsyncIntraBandENDC | Apple |
| R2-2401291 | Update on UE capability AsyncIntraBandENDC | Apple |
| R2-2401292 | Update on UE capability AsyncIntraBandENDC | Apple |
| R2-2401293 | Update on UE capability AsyncIntraBandENDC | Apple |
| R2-2401346 | Discussion on max data rate calculation | Sequans Communications |
| R2-2401540 | Update on UE capability AsyncIntraBandENDC | Apple |
| R2-2401558 | [Post125][763][SRS-only cell] Bandwidth of the SRS-only Cell (ZTE) | ZTE Corporation, Sanechips |
| R2-2401753 | Clarification on UE capability segmentation | Huawei, HiSilicon |
| R2-2401754 | Clarification on UE capability segmentation | Huawei, HiSilicon |
| R2-2401755 | Clarification on UE capability segmentation | Huawei, HiSilicon |
| R2-2401756 | Clarification on ca-ParametersNRDC capability (Understanding#2) | Huawei, HiSilicon |
| R2-2401757 | Clarification on ca-ParametersNRDC capability (Understanding#2) | Huawei, HiSilicon |
| R2-2401758 | Clarification on ca-ParametersNRDC capability (Understanding#2) | Huawei, HiSilicon |
| R2-2401759 | Clarification on ca-ParametersNRDC capability (Understanding#2) | Huawei, HiSilicon |
| R2-2401831 | Update on UE capability AsyncIntraBandENDC | Apple, Nokia, Nokia Shanghai Bell |
| R2-2401832 | Update on UE capability AsyncIntraBandENDC | Apple, Nokia, Nokia Shanghai Bell |
| R2-2401833 | Update on UE capability AsyncIntraBandENDC | Apple, Nokia, Nokia Shanghai Bell |
| R2-2401936 | Summary of [AT125][763] Clarification on the Supported Bandwidth of the SRS-only Cell (ZTE) | ZTE Corporation, Sanechips |
| 5.2 | NR V2X | |
| R2-2400368 | Correction for terminating on-going RACH due to pending SR for SL-BSR | Lenovo |
| R2-2400519 | Misc RRC corrections for NR V2X | Huawei, HiSilicon (Rapporteur), OPPO |
| R2-2400520 | Misc RRC corrections for NR V2X | Huawei, HiSilicon (Rapporteur), OPPO |
| R2-2400521 | Misc RRC corrections for NR V2X | Huawei, HiSilicon, OPPO |
| R2-2400707 | Discussion on stop of ongoing RACH due to SR for SL-BSR | CATT, Lenovo, LG Electronics, OPPO, Apple, ASUSTek, Xiaomi, Huawei, HiSilicon |
| R2-2400708 | CR on termination of on-going RACH due to pending SR for SL-BSR | CATT, Lenovo, ASUSTek |
| R2-2400709 | CR on termination of on-going RACH due to pending SR for SL-BSR | CATT, Lenovo, ASUSTek |
| R2-2400710 | CR on termination of on-going RACH due to pending SR for SL-BSR | CATT, Lenovo, ASUSTek |
| R2-2400794 | Latency bound requirement of NR SL CSI report | MediaTek Inc. |
| R2-2400910 | Latency bound requirement of NR SL CSI report | MediaTek Inc. |
| R2-2400911 | Latency bound requirement of NR SL CSI report | MediaTek Inc. |
| R2-2401011 | Miscellaneous corrections on TS 38.321 | LG Electronics France |
| R2-2401789 | Misc RRC corrections for NR V2X | Huawei, HiSilicon (Rapporteur), OPPO |
| R2-2401790 | Miscellaneous corrections on TS 38.321 | LG |
| R2-2401791 | Miscellaneous corrections on TS 38.321 | LG |
| R2-2401852 | Miscellaneous corrections on TS 38.321 | LG |
| R2-2401865 | CR on termination of on-going RACH due to pending SR for SL-BSR | CATT, Lenovo, ASUSTek |
| R2-2401866 | CR on termination of on-going RACH due to pending SR for SL-BSR | CATT, Lenovo, ASUSTek |
| R2-2401867 | CR on termination of on-going RACH due to pending SR for SL-BSR | CATT, Lenovo, ASUSTek |
| R2-2402056 | Miscellaneous corrections on TS 38.321 | LG |
| R2-2402057 | Miscellaneous corrections on TS 38.321 | LG |
| 5.3 | NR Positioning Support | |
| R2-2401198 | Corrections to NR-DL-PRS-Info | Nokia, Nokia Shanghai Bell |
| R2-2401323 | RIL E138 SBAS-ID Field Description | Ericsson |
| R2-2401342 | Discussion on contents of ProvideLocationInformation | NTT DOCOMO, INC., SK telecom |
| R2-2401343 | Change on contents of ProvideLocationInformation (Rel-16) | NTT DOCOMO, INC., SK telecom |
| R2-2401344 | Change on contents of ProvideLocationInformation (Rel-17) | NTT DOCOMO, INC., SK telecom |
| R2-2401345 | Change on contents of ProvideLocationInformation (Rel-18) | NTT DOCOMO, INC., SK telecom |
| R2-2401618 | Corrections to NR-DL-PRS-Info | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2401619 | Corrections to NR-DL-PRS-Info | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2401620 | Corrections to NR-DL-PRS-Info | Nokia, Nokia Shanghai Bell, Ericsson |
| 6.1 | Common | |
| R2-2400288 | Correction on initialization of RRC parameter in RA procedure | Xiaomi |
| R2-2400289 | Correction on initialization of RRC parameter in RA procedure | Xiaomi |
| 6.1.1 | Stage 2 and Organisational | |
| R2-2400011 | LS on NCD-SSB time offset for RedCap UEs in TDD (R1-2310566; contact: Ericsson) | RAN1 |
| R2-2400016 | RLS to RAN2 on introduction of simultaneous PUCCH and PUSCH transmission with same priority (R1-2312456; contact: Samsung) | RAN1 |
| R2-2400018 | LS on PBCH payload of NCD-SSB (R1-2312520; contact: Eroicsson) | RAN1 |
| R2-2400019 | Reply LS on monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs (R1-2312522; contact: Ericsson) | RAN1 |
| R2-2400025 | LS on periodicity of TRS resources for idle/inactive UEs (R1-2312620; contact: Ericsson) | RAN1 |
| R2-2400030 | LS on skipping UL transmission and R17 TBoMS (R1-2312651; contact: Huawei) | RAN1 |
| R2-2400041 | Reply LS on the user consent for trace reporting (R3-237964; contact: Ericsson) | RAN3 |
| R2-2400048 | LS on the new channel bandwidth class for FR2-2 (R4-2315865; contact: Huawei) | RAN4 |
| R2-2400058 | Further reply LS on higher power limit capability for inter-band UL DC (R4-2321905; contact Apple) | RAN4 |
| R2-2400081 | Reply LS on the user consent for trace reporting (S2-2401578; contact: Ericsson) | SA2 |
| R2-2400128 | Discussion and draft reply LS on skipping UL transmission and R17 TBoMS | Huawei, HiSilicon (Contact company) |
| R2-2400218 | Reply LS on the user consent for trace reporting (S5-241084; contact: Ericsson) | SA5 |
| R2-2400471 | Handover for Reduced Capability | Nokia (Rapporteur), Qualcomm, Nokia Shanghai Bell |
| R2-2400472 | Handover for Reduced Capability | Nokia (Rapporteur), Qualcomm, Nokia Shanghai Bell |
| R2-2400473 | Handover for Reduced Capability | Nokia (Rapporteur), Qualcomm, Nokia Shanghai Bell |
| R2-2400474 | Handover for Reduced Capability | Nokia (Rapporteur), Qualcomm, Nokia Shanghai Bell |
| R2-2400588 | Discussion on TBoMS and UL Skipping | Ericsson |
| R2-2400928 | Discussion on Skipping UL transmission and R17 TBoMS | Apple |
| R2-2400929 | Correction on Skipping UL transmission and R17 TBoMS | Apple |
| R2-2400963 | Description of MBS FSA ID | Nokia, Nokia Shanghai Bell |
| R2-2401049 | Considerations on periodicity of TRS resources for idle/inactive UEs | ZTE Corporation,Sanechips |
| R2-2401299 | RACH resources while SDT procedure is ongoing | Nokia, Samsung, Nokia Shanghai Bell |
| R2-2401300 | RACH resources while SDT procedure is ongoing | Nokia, Samsung, Nokia Shanghai Bell |
| R2-2401350 | Corrections on the TRS in Idle and Inactive | Ericsson |
| R2-2401351 | Clarification on TRS in idle and inactive | Ericsson |
| R2-2401352 | Correction on TRS in idle and inactive | Ericsson |
| R2-2401353 | DRAFT Reply LS on periodicity of TRS resources for idle/inactive UEs | Ericsson |
| R2-2401722 | Reply LS on skipping UL transmission and R17 TBoMS | RAN2 |
| R2-2401723 | RRC CR for clarification on R16 skipping UL transmission and R17 TBoMS | Huawei, HiSilicon, Ericsson, Apple, CATT |
| R2-2401724 | RRC CR for clarification on R16 skipping UL transmission and R17 TBoMS | Huawei, HiSilicon, Ericsson, Apple, CATT |
| R2-2401742 | Report of [AT125][752][TRS] TRS in Idle and Inactive (Ericsson) | Ericsson |
| R2-2401816 | LS on IE supportedBandwidthCombinationSetIntraENDC and IE intraBandENDC-Support (R4-2403809; contact: Google) | RAN4 |
| 6.1.1.1 | Other | |
| R2-2400129 | Clarification on R16 skipping UL transmission and R17 TBoMS | Huawei, HiSilicon |
| R2-2400130 | Clarification on R16 skipping UL transmission and R17 TBoMS | Huawei, HiSilicon |
| R2-2400870 | Discussion on LS reply to skipping UL transmission and R17 TBoMS | Sharp |
| R2-2401112 | Correction on service link types for GSO | MediaTek Inc., Nokia (Rapporteur), Intel |
| R2-2401116 | Correction on service link types for GSO | MediaTek Inc., Nokia (Rapporteur), Intel |
| 6.1.2 | User Plane corrections | |
| R2-2400097 | Correction in TS 38.300 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | CATT |
| R2-2400098 | Correction in TS 38.300 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | CATT |
| R2-2400099 | Correction in TS 38.321 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | CATT |
| R2-2400100 | Correction in TS 38.321 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | CATT |
| R2-2400805 | Classification the start time of drx-HARQ-RTT-TimerUL when grant collision | MediaTek Inc. |
| R2-2400907 | Classification the start time of drx-HARQ-RTT-TimerUL when grant collision | MediaTek Inc. |
| R2-2400965 | Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | Samsung |
| R2-2400966 | Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | Samsung |
| R2-2401050 | Clarification On Enhanced PHR MAC CE For PUSCH Repetition with mTRP | ZTE Corporation,Sanechips |
| R2-2401051 | Clarification On Enhanced PHR MAC CE For PUSCH Repetition with mTRP | ZTE Corporation,Sanechips |
| R2-2401271 | Clarification on drx-HARQ-RTT-TimerUL for TTIB | Huawei, HiSilicon |
| R2-2401272 | Clarification on drx-HARQ-RTT-TimerUL for TTIB | Huawei, HiSilicon |
| R2-2401301 | Correction on sdt-LogicalChannelSR-DelayTimer applicability | Nokia, Nokia Shanghai Bell |
| R2-2401302 | Correction on sdt-LogicalChannelSR-DelayTimer applicability | Nokia, Nokia Shanghai Bell |
| R2-2401838 | Correction in TS 38.300 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | CATT |
| R2-2401839 | Correction in TS 38.300 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | CATT |
| R2-2401840 | Correction in TS 38.321 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | CATT, Samsung |
| R2-2401875 | Correction in TS 38.321 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | CATT, Samsung |
| 6.1.2.1 | Other | |
| R2-2400454 | Clearification on resource set in MAC and RRC | vivo, Guangdong Genius |
| R2-2400542 | Correction to NOTEs Numbering | Mediatek Inc. |
| R2-2400614 | Discussion on the looped RACH case for RedCap | Huawei, HiSilicon, Mediatek, ZTE Corporation, Sanechips, CMCC, Qualcomm Incorporated, LG Electronics |
| R2-2400897 | Correction on CG-SDT initial transmission (R17) | LG Electronics Inc. |
| R2-2400898 | Correction on CG-SDT initial transmission (R18) | LG Electronics Inc. |
| R2-2400936 | Clarification on HARQ RTT Timer operation when drx-LastTransmissionUL is configured | Apple |
| R2-2401296 | Clarification on HARQ RTT Timer operation when drx-LastTransmissionUL is configured | Apple, Qualcomm Incorporated |
| R2-2401297 | Clarification on HARQ RTT Timer operation when drx-LastTransmissionUL is configured | Apple, Qualcomm Incorporated |
| R2-2401498 | Correction on CG-SDT initial transmission | LG Electronics Inc. |
| R2-2401499 | Correction on CG-SDT initial transmission (R18) | LG Electronics Inc. |
| R2-2401517 | Clarification on HARQ RTT Timer operation when drx-LastTransmissionUL is configured | Apple, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, MediaTek Inc., Huawei, HiSilicon |
| R2-2401518 | Clarification on HARQ RTT Timer operation when drx-LastTransmissionUL is configured | Apple, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, MediaTek Inc., Huawei, HiSilicon |
| R2-2401841 | Correction on CG-SDT initial transmission | LG Electronics Inc. |
| R2-2401842 | Correction on CG-SDT initial transmission | LG Electronics Inc. |
| 6.1.3.1 | NR RRC | |
| R2-2400026 | LS on Rel-17 URLLC/IIoT required RRC parameter description change in 38.331 (R1-2312621; contact: Nokia) | RAN1 |
| R2-2400059 | LS on R17 DC location signaling (R4-2321950; contact: vivo) | RAN4 |
| R2-2400110 | Discussion on DC location RRC signaling | CATT, Huawei, HiSilicon |
| R2-2400111 | DRAFT Reply LS on R17 DC location signaling | CATT, Huawei, HiSilicon |
| R2-2400142 | Clarification on MIB associated with NCD-SSB | Qualcomm Incorporated, Ericsson, Huawei, HiSilicon, ZTE, Sanechips |
| R2-2400143 | Clarification on UE’s behavior after MIB reception | Qualcomm Incorporated, Ericsson, Huawei, HiSilicon, ZTE, Sanechips |
| R2-2400169 | Discussion on R17 DC location signalling | vivo |
| R2-2400170 | Correction on R17 DC location signalling | vivo |
| R2-2400171 | Draft Reply LS on R17 DC location signaling | vivo |
| R2-2400212 | Correction to PDCCH configuration of RedCap-specific initial BWP | MediaTek Inc. |
| R2-2400213 | Correction to PDCCH configuration of (e)RedCap-specific initial BWP | MediaTek Inc. |
| R2-2400455 | Correction on NCD-SSB for RedCap | Vivo, Guangdong Genius |
| R2-2400554 | Correction on the reporting of TAC in Random access report | Fujitsu |
| R2-2400555 | Correction on the reporting of TAC in Random access report | Fujitsu |
| R2-2400592 | Discussion on periodicity of TRS resources for idle-inactive UEs | Huawei, HiSilicon |
| R2-2400758 | Field conditions for MUSIM gap | Ericsson |
| R2-2400759 | Field conditions for MUSIM gap | Ericsson |
| R2-2400821 | Corrections on uplink power control in unified TCI framework | Huawei, HiSilicon |
| R2-2400822 | Corrections on uplink power control in unified TCI framework (R18 shadow CR) | Huawei, HiSilicon |
| R2-2400828 | Correction on Redcap 1 Rx and 2 Rx barring | Nokia, Nokia Shanghai Bell |
| R2-2400829 | Correction on Redcap 1 Rx and 2 Rx barring | Nokia, Nokia Shanghai Bell |
| R2-2400964 | MBS frequencies of interest determination | Nokia, Nokia Shanghai Bell |
| R2-2400972 | Correction on cg-UCI-Multiplexing | Nokia, Nokia Shanghai Bell |
| R2-2400973 | Correction on cg-UCI-Multiplexing | Nokia, Nokia Shanghai Bell |
| R2-2400980 | Correction on FD-FDD capability checking for RedCap UE in TDD band | LG electronics, Huawei |
| R2-2400981 | Correction on FD-FDD capability checking for RedCap UE in TDD band | LG Electronics Inc, Huawei |
| R2-2401206 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2401207 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2401208 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2401209 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2401220 | Clarification of frequencyDomainAllocation in TRS-ResourceSet-r17 | MediaTek Inc. |
| R2-2401227 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2401228 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2401348 | Open issues RLM/BFD relaxation | Ericsson |
| R2-2401349 | MBS and paging during SDT | Ericsson |
| R2-2401433 | Clarification on RACH-ConfigCommon used in CFRA | ZTE Corporation, Qualcomm Incorporated |
| R2-2401434 | Correction on RACH-ConfigCommon for CFRA | ZTE Corporation, Qualcomm Incorporated |
| R2-2401435 | Correction on RACH-ConfigCommon for CFRA | ZTE Corporation, Qualcomm Incorporated |
| R2-2401725 | Clarification on MIB associated with NCD-SSB | Qualcomm Incorporated, Ericsson, Huawei, HiSilicon, ZTE, Sanechips |
| R2-2401726 | Clarification on UE’s behavior after MIB reception | Qualcomm Incorporated, Ericsson, Huawei, HiSilicon, ZTE, Sanechips |
| R2-2401727 | Correction to PDCCH configuration of RedCap-specific initial BWP | MediaTek Inc. |
| R2-2401728 | Correction to PDCCH configuration of (e)RedCap-specific initial BWP | MediaTek Inc. |
| R2-2401729 | Correction on FD-FDD capability checking for RedCap UE in TDD band | LG electronics, Huawei, Ericsson |
| R2-2401730 | Correction on FD-FDD capability checking for RedCap UE in TDD band | LG electronics, Huawei, Ericsson |
| R2-2401731 | Correction on the reporting of TAC in Random access report | Fujitsu |
| R2-2401732 | Correction on the reporting of TAC in Random access report | Fujitsu |
| R2-2401733 | Corrections on uplink power control in unified TCI framework | Huawei, HiSilicon |
| R2-2401734 | Corrections on uplink power control in unified TCI framework | Huawei, HiSilicon |
| R2-2401735 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2401736 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2401764 | Report of [AT125][764] Prioritization between unicast and SIB broadcast (Ericsson) | Ericsson |
| R2-2401765 | Clarification on RACH-ConfigCommon for CFRA | ZTE Corporation, Qualcomm Incorporated, Ericsson |
| R2-2401766 | Clarification on RACH-ConfigCommon for CFRA | ZTE Corporation, Qualcomm Incorporated, Ericsson |
| R2-2401767 | Reply LS on R17 DC location signaling | RAN2 |
| R2-2401957 | Summary of [AT125][754] Correction on the reporting of TAC in Random access report | Fujitsu |
| 6.1.3.2 | UE capabilities | |
| R2-2400047 | Reply LS on the CA Aggregated BW capability signaling by the UE (R4-2322003; contact: Qualcomm) | RAN4 |
| R2-2400237 | Discussion on Maximum Aggregated Bandwidth Capability | OPPO |
| R2-2400351 | Concluding on maximum aggregated BW UE capability | Qualcomm Incorporated |
| R2-2400352 | Introduction of maximum aggregated bandwidth for FR1 CA and for FR2 intra-band CA | Qualcomm Incorporated, Ericsson, T-Mobile USA |
| R2-2400353 | Introduction of maximum aggregated bandwidth for FR1 CA and for FR2 intra-band CA | Qualcomm Incorporated, Ericsson, T-Mobile USA |
| R2-2400354 | Introduction of maximum aggregated bandwidth for FR1 CA and for FR2 intra-band CA | Qualcomm Incorporated, Ericsson, T-Mobile USA |
| R2-2400355 | Introduction of maximum aggregated bandwidth for FR1 CA and for FR2 intra-band CA | Qualcomm Incorporated, Ericsson, T-Mobile USA |
| R2-2400517 | Correction on the UE capability of survival time | Huawei, HiSilicon |
| R2-2400518 | Correction on the UE capability of survival time | Huawei, HiSilicon |
| R2-2400628 | Removal of references to unknown RAN4 specification | Lenovo |
| R2-2400629 | Removal of references to unknown RAN4 specification | Lenovo |
| R2-2400630 | Removal of references to unknown RAN4 specification | Lenovo |
| R2-2400631 | Removal of references to unknown RAN4 specification | Lenovo |
| R2-2400704 | CEF and RLF reporting for RedCap UEs | MediaTek Inc. |
| R2-2400705 | CEF and RLF reporting for (e)RedCap UEs | MediaTek Inc. |
| R2-2400719 | Clarification on capabilities of mixed codebook | Huawei, HiSilicon |
| R2-2400720 | Clarification on capabilities of mixed codebook | Huawei, HiSilicon |
| R2-2400721 | Discussion on CA aggregated bandwidth capability | Huawei, HiSilicon |
| R2-2400863 | Discussion on BCS5 capability signalling | Nokia, Nokia Shanghai Bell |
| R2-2401026 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16(r16) | ZTE Corporation, Sanechips |
| R2-2401027 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16(r17) | ZTE Corporation, Sanechips |
| R2-2401028 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16(r18) | ZTE Corporation, Sanechips |
| R2-2401029 | Consideration on the Aggragated Bandwidth for the NR-DC Case | ZTE Corporation, Sanechips |
| R2-2401030 | Clarification on the Parallel Tx Capability | ZTE Corporation, Sanechips |
| R2-2401031 | Correction on Prerequisite Feature for parallelTxMsgA-SRS-PUCCH-PUSCH-intraBand-r17(r17) | ZTE Corporation, Sanechips |
| R2-2401032 | Correction on Prerequisite Feature for parallelTxMsgA-SRS-PUCCH-PUSCH-intraBand-r17(r18) | ZTE Corporation, Sanechips |
| R2-2401519 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16 (r16) | ZTE Corporation, Sanechips |
| R2-2401520 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16 (r17) | ZTE Corporation, Sanechips |
| R2-2401521 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16 (r18) | ZTE Corporation, Sanechips |
| R2-2401737 | Introduction of maximum aggregated bandwidth for FR1 CA and for FR2 intra-band CA | Qualcomm Incorporated, Ericsson, T-Mobile USA |
| R2-2401738 | Introduction of maximum aggregated bandwidth for FR1 CA and for FR2 intra-band CA | Qualcomm Incorporated, Ericsson, T-Mobile USA |
| R2-2401739 | Introduction of maximum aggregated bandwidth for FR1 CA and for FR2 intra-band CA | Qualcomm Incorporated, Ericsson, T-Mobile USA |
| R2-2401740 | Introduction of maximum aggregated bandwidth for FR1 CA and for FR2 intra-band CA | Qualcomm Incorporated, Ericsson, T-Mobile USA |
| R2-2401741 | LS on Paralle Tx Capability | RAN2 |
| R2-2401801 | Reply LS on maximum aggregated bandwidth for FR1 inter-band CA (R4-2401517; contact: vivo) | RAN4 |
| R2-2401872 | Reply LS on maximum aggregated bandwidth for FR1 inter-band CA (R4-2401517; contact: vivo) | RAN4 |
| 6.1.3.3 | Other | |
| R2-2400993 | Correction to 38.331 on last used cell for PEI | OPPO |
| R2-2400994 | Correction to 38.331 on last used cell for PEI | OPPO |
| R2-2400995 | Correction to 38.304 on last used cell for PEI | OPPO |
| R2-2400996 | Correction to 38.304 on last used cell for PEI | OPPO |
| 6.2 | NR Sidelink relay | |
| R2-2400396 | Correction on pre-configuration usage | Xiaomi |
| R2-2400557 | SRAP-related corrections to 38.300 | Samsung |
| R2-2400558 | SRAP-related corrections to 38.300 | Samsung |
| R2-2400648 | Discussion on AS condition checking for SUI transmission | OPPO |
| R2-2400649 | Miscellaneous corrections for NR sidelink relay enhancements | OPPO (Rapporteur) |
| R2-2400650 | Miscellaneous corrections for NR sidelink relay enhancements | OPPO (Rapporteur) |
| R2-2400690 | Correction on the SRBs of L2 U2N Remote UE | ZTE, Sanechips |
| R2-2400731 | Miscellaneous RRC corrections for Rel-17 SL relay | Huawei, HiSilicon, OPPO |
| R2-2400732 | Miscellaneous RRC corrections for SL relay | Huawei, HiSilicon, OPPO |
| R2-2400733 | Clarification on the case SL frequency is not included in SIB12 | Huawei, HiSilicon |
| R2-2400734 | Clarification on the case SL frequency is not included in SIB12 | Huawei, HiSilicon |
| R2-2400764 | Considerations on applicability of SIB12 received via relay connection | Nokia, Nokia Shanghai Bell |
| R2-2400945 | Correction on logical channel identity | Apple |
| R2-2401109 | Correction on the SRBs of L2 U2N Remote UE | ZTE, Sanechips |
| R2-2401153 | Clarification on preconfiguration usage in U2N relay | Qualcomm Incorporated |
| R2-2401484 | Correction on pre-configuration usage | Xiaomi |
| R2-2401611 | [Relay] Summary of Rel-17 RRC corrections in AI 6.2 | Huawei, HiSilicon |
| R2-2401621 | Misc RRC corrections for SL relay | Huawei, HiSilicon, OPPO, Apple, ZTE, Philips International B.V |
| R2-2401622 | Misce RRC corrections for SL relay | Huawei, HiSilicon, OPPO, Apple, ZTE, Philips International B.V |
| R2-2401623 | Miscellaneous corrections for NR sidelink relay enhancements | OPPO (Rapporteur) |
| R2-2401624 | Miscellaneous corrections for NR sidelink relay enhancements | OPPO (Rapporteur) |
| R2-2401625 | Clarification on the case SL frequency is not included in SIB12 | Huawei, HiSilicon, ZTE, Apple |
| R2-2401626 | Clarification on the case SL frequency is not included in SIB12 | Huawei, HiSilicon, ZTE, Apple |
| R2-2401627 | Applicability of SIB12 configuration for a L2 Remote UE | Nokia, Nokia Shanghai Bell |
| R2-2401628 | Applicability of SIB12 configuration for a L2 Remote UE | Nokia, Nokia Shanghai Bell |
| R2-2401720 | [Relay RIL list] | Huawei |
| R2-2401914 | Miscellaneous corrections for NR sidelink relay enhancements | OPPO (Rapporteur) |
| R2-2401915 | Miscellaneous corrections for NR sidelink relay enhancements | OPPO (Rapporteur) |
| R2-2402046 | Correction on pre-configuration usage | Xiaomi |
| R2-2402047 | Correction on pre-configuration usage | Xiaomi |
| 6.3 | NR Non-Terrestrial Networks (NTN) | |
| R2-2400610 | Minor correction for NTN in 38.304 | ZTE Corporation, Sanechips |
| R2-2400997 | Correction to 38.331 for NR NTN | OPPO |
| R2-2400998 | Correction to 38.331 for NR NTN | OPPO |
| R2-2401118 | Corrections on usage of LEO, GEO, GSO and NGSO | MediaTek Inc., Nokia, Nokia Shanghai Bell, Intel (Rapporteur) |
| R2-2401120 | Corrections on usage of LEO, GEO, GSO and NGSO | MediaTek Inc., Nokia, Nokia Shanghai Bell, Intel (Rapporteur) |
| R2-2401335 | Clarification on HARQ mode for SRB4 | Google Inc. |
| R2-2401336 | Clarification on HARQ mode for SRB4 | Google Inc. |
| R2-2401586 | Correction to 38.331 for NR NTN | Ericsson, Google, OPPO |
| R2-2401587 | Correction to 38.331 for NR NTN | OPPO |
| R2-2401588 | Minor correction for NTN in 38.304 | ZTE Corporation, Sanechips |
| R2-2401800 | Reply LS on the service requirement of restricting satellite access RAT type (R3-241204; contact: Ericsson) | RAN3 |
| R2-2401920 | Minor correction for NTN in 38.304 | ZTE Corporation, Sanechips |
| R2-2401922 | Corrections on usage of LEO, GEO, GSO and NGSO | MediaTek Inc., Nokia, Nokia Shanghai Bell, Intel (Rapporteur) |
| R2-2401923 | Corrections on usage of LEO, GEO, GSO and NGSO | MediaTek Inc., Nokia, Nokia Shanghai Bell, Intel (Rapporteur) |
| R2-2401979 | Correction to 38.331 for NR NTN | OPPO, Google, Ericsson |
| R2-2402050 | Minor correction for NTN in 38.304 | ZTE Corporation, Sanechips |
| R2-2402060 | Minor correction for NTN in 38.304 | ZTE Corporation, Sanechips |
| 6.4.1 | General and stage 2 | |
| R2-2400008 | LS Out Sub One Second Report Period for Deferred Location over SBI (C4-234472; contact: Ericsson) | CT1 |
| R2-2401319 | Missing LPP support for sub 1s location information reporting periodicity | Ericsson |
| 6.4.2 | Stage 3 (RRC/LPP/MAC/UE capabilities) | |
| R2-2401154 | Correction to LPP spec in R17 | Huawei, HiSilicon |
| 6.6 | NR Sidelink enhancements | |
| R2-2400149 | Correction on tx profile for SL DRX | ZTE Corporation, Sanechips |
| R2-2400150 | Correction on tx profile for SL DRX | ZTE Corporation, Sanechips |
| R2-2400397 | Correction on SL DRX | Xiaomi |
| R2-2400516 | Coexistence between SL DRX and SL IUC | Ericsson |
| R2-2400883 | Correction on SL DRX for broadcast and groupcast handling missed in RRC reconfiguration | ASUSTeK |
| R2-2400971 | Miscellaneous corrections on TS 38.321 | LG Electronics France, Apple |
| R2-2401485 | Correction on SL DRX | Xiaomi |
| R2-2401522 | Correction on tx profile for SL DRX | ZTE Corporation, Sanechips |
| R2-2401523 | Correction on tx profile for SL DRX | ZTE Corporation, Sanechips |
| R2-2401792 | Correction on SL DRX for broadcast and groupcast handling missed in RRC reconfiguration | ASUSTeK |
| R2-2401793 | Miscellaneous corrections on TS 38.321 | LG, Apple |
| R2-2401853 | Miscellaneous corrections on TS 38.321 | LG, Apple |
| R2-2402043 | Correction on SL DRX for broadcast and groupcast handling missed in RRC reconfiguration | ASUSTeK |
| R2-2402044 | Correction on SL DRX for broadcast and groupcast handling missed in RRC reconfiguration | ASUSTeK |
| R2-2402058 | Miscellaneous corrections on TS 38.321 | LG, Apple |
| 7.0.1 | UE Capabilites | |
| R2-2400020 | LS on Rel-18 higher-layers parameter list (R1-2312710; contact: Ericsson) | RAN1 |
| R2-2400021 | LS on updates to the Rel-18 RAN1 UE features list for NR after RAN1#115 (R1-2312707; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2400023 | LS on Rel-18 RAN1 UE features list for NR after RAN1#115 (R1-2308568; contact: Samsung) | RAN1 |
| R2-2400031 | LS on Rel-18 higher-layers parameter list (R1-2312661; contact: Ericsson) | RAN1 |
| R2-2400056 | LS on RAN4 UE feature list for Rel-18 (R4-2321730; contact: CMCC) | RAN4 |
| R2-2400057 | LS on RAN4 UE feature list for Rel-18 (version 2) (R4-2321823; contact: CMCC) | RAN4 |
| R2-2400381 | Draft CR on UE capability 38.306 for Rel-18 R1 feature lists and corrections | Intel Corporation |
| R2-2400382 | Draft CR on UE capability 38.331 for Rel-18 R1 feature lists and corrections | Intel Corporation |
| R2-2400383 | [Draft] Reply LS on UE capability open issues regarding to Rel-18 RAN1 UE features list for NR | Intel Corporation |
| R2-2400904 | Remaining issues in RAN1 feature list | Samsung |
| R2-2401570 | [LS to RAN1 on Parameter Lists] | Ericsson |
| R2-2401690 | Corrections and Updates to UE capabilities for Rel-18 WIs, including TEI18 [HARQ-ACK MUX on PUSCH], [LCID-extension], [RA-SDT_BeamFailure] | Intel Corporation |
| R2-2401691 | Corrections and Updates to UE capabilities for Rel-18 WIs, including TEI18 [HARQ-ACK MUX on PUSCH] | Intel Corporation |
| R2-2401702 | LS on Rel-18 RAN1 UE features list for NR after RAN1#116 (R1-2401711; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2401808 | LS on RAN4 UE feature list for Rel-18 (version 3) (R4-2403636; contact: CMCC) | RAN4 |
| R2-2401834 | LS on questions and recommendations to Rel-18 RAN1 UE features list | RAN2 |
| R2-2401968 | NR ASN.1 Class 0 Issues per WI | Ericsson |
| R2-2402054 | Corrections and Updates to UE capabilities for Rel-18 WIs, including TEI18 [HARQ-ACK MUX on PUSCH], [LCID-extension], [RA-SDT_BeamFailure] | Intel Corporation |
| R2-2402055 | Corrections and Updates to UE capabilities for Rel-18 WIs, including TEI18 [HARQ-ACK MUX on PUSCH] | Intel Corporation |
| 7.0.2 | CCCH LCID extension | |
| R2-2401269 | Correction to 38.306 on capability description of CCCH LCID extension | Huawei, HiSilicon |
| R2-2401673 | Correction to 38.306 on capability description of CCCH LCID extension [LCID-extension] | Huawei, HiSilicon |
| R2-2401835 | Correction to 38.306 on capability description of CCCH LCID extension | Huawei, HiSilicon |
| 7.0.3 | ASN.1 Review | |
| R2-2400192 | [H059] CIO for UAV events | Huawei, HiSilicon |
| R2-2400239 | Discussion on [O310, O311] | OPPO |
| R2-2400240 | Discussion on [B009] | OPPO, Lenovo |
| R2-2400331 | [H608][B011][I110] Discussion on needM within a list | Huawei, HiSilicon |
| R2-2400332 | [H506] Guideline for the usage of late non-critical extension | Huawei, HiSilicon |
| R2-2400623 | Discussion on common ASN.1 issues (B011, I110, H608, B016, C616) | Lenovo |
| R2-2400624 | [DRAFT] LS reply on Rel-18 RAN1 NR UE features and higher layers parameter list | Lenovo |
| R2-2400823 | Recommendations for ASN.1 review | Huawei, HiSilicon |
| R2-2400824 | [H031][H069] Uninformative and redundant field descriptions | Huawei, HiSilicon |
| R2-2400843 | Miscellaneous corrections from ASN.1 review | Ericsson |
| R2-2400844 | RIL List for MULTI/Gen issues | Ericsson |
| R2-2401034 | Clarification on multi-path with MCG [E105] | LG Electronics France |
| R2-2401035 | Clarification on multi-path with MCG [E105] | LG Electronics France |
| R2-2401187 | [H502] Discussion on odSIB request in RRC_CONNECTED for R18 SIBs | Huawei, HiSilicon |
| R2-2401270 | [H071] Discussion on paging collision between group paging and MT-SDT paging | Huawei, HiSilicon |
| R2-2401327 | Discussion on use of late non-critical extensions (B001 LTE, H506 NR) | Lenovo |
| R2-2401368 | Discussion on extending transaction ID space [E074] | Ericsson |
| R2-2401369 | Correction to CG RACH-less MAC procedure [C704, E052, C604, H507] | Ericsson |
| R2-2401497 | [H506] Guideline for the usage of late non-critical extension | Huawei, HiSilicon |
| R2-2401530 | NR ASN.1 Review file | Ericsson |
| R2-2401531 | NR RIL List | Ericsson |
| R2-2401532 | NR ASN.1 Class 0 Issues | Ericsson |
| R2-2401836 | RIL List for MULTI/Gen issues | Ericsson |
| R2-2401974 | Miscellaneous corrections from ASN.1 review | Ericsson |
| R2-2401975 | RIL List for MULTI/Gen issues after RAN#125 | Ericsson |
| R2-2401976 | [Merged ASN.1 RIL list] | Ericsson |
| R2-2402062 | Miscellaneous corrections from ASN.1 review | Ericsson |
| 7.0.4 | Other | |
| R2-2400329 | Correction on RACH resource set selection for CFRA | Huawei, HiSilicon |
| R2-2400330 | Clarification on the expression of "if configured" in the MAC spec | Huawei, HiSilicon |
| R2-2400333 | [C704][E052][C604][H507] Discussion on CG RACH-less in LTM, NTN and mIAB in R18 | Huawei, HiSilicon, CATT, Ericsson, ZTE Corporation |
| R2-2400334 | [C704][E052][C604][H507] Correction to CG RACH-less MAC procedure in R18 | Huawei, HiSilicon, CATT, Ericsson, ZTE Corporation |
| R2-2400384 | Discussion on mobile IAB-MT UE capability | Intel Corporation |
| R2-2400475 | Misellaneous Corrections | Nokia (Rapporteur) |
| R2-2400685 | Specification handling of mIAB and NTN RACH-less handover capabilities | Samsung |
| R2-2400999 | Discussion on open issues on RACH-less HO | OPPO |
| R2-2401164 | RACHless HO support in release 18 | Nokia, Nokia Shanghai Bell |
| R2-2401165 | RACHless HO support in release 18 | Nokia, Nokia Shanghai Bell |
| R2-2401166 | RACHless HO support in release 18 | Nokia, Nokia Shanghai Bell |
| R2-2401167 | RACHless HO support in release 18 | Nokia, Nokia Shanghai Bell |
| R2-2401168 | RACHless HO support in release 18 | Nokia, Nokia Shanghai Bell |
| R2-2401303 | Correction on HARQ buffer flush at SCG deactivation | Nokia, Apple, Mediatek, Qualcomm, Nokia Shanghai Bell |
| R2-2401370 | Correction to CG RACH-less RRC procedure [C704, E052, C604, H507] | Ericsson, Huawei, HiSilicon, CATT, ZTE Corporation |
| R2-2401378 | Extending support of IAB-NTN RACH-less HO for legacy L3 handover | Ericsson |
| R2-2401524 | RACHless HO support in release 18 | Nokia, Nokia Shanghai Bell |
| R2-2401574 | Generalization of RACH-less handover | Ericsson, Huawei, HiSilicon, CATT, ZTE Corporation |
| R2-2401686 | Generalization of RACH-less handover for MAC spec [RACH-lessHO] | Huawei, HiSilicon |
| R2-2401967 | Offline on RACH-less HO capabilities | Samsung |
| R2-2401973 | Correction on HARQ buffer flush at SCG deactivation | Nokia, Apple, Mediatek, Qualcomm, Nokia Shanghai Bell |
| R2-2402030 | Generalization of RACH-less handover [RACH-lessHO] | Ericsson, Huawei, HiSilicon, CATT, ZTE Corporation |
| R2-2402069 | Generalization of RACH-less handover [RACH-lessHO] | Ericsson, Huawei, HiSilicon, CATT, ZTE Corporation |
| 7.1 | NR network-controlled repeaters | |
| R2-2401671 | [AT125][651][NCR] Corrections (Apple) | Apple (Session Chair) |
| 7.1.1 | Organizational | |
| R2-2401387 | Clarification to Network-Controlled Repeaters Stage-2 description | Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2401436 | Miscellaneous RRC corrections for Network-controlled repeaters | ZTE Corporation (Rapporteur) |
| R2-2401437 | RILs conclusion for NCR | ZTE Corporation |
| R2-2401677 | Miscellaneous RRC corrections for Network-controlled repeaters | ZTE Corporation (Rapporteur) |
| R2-2401683 | Miscellaneous RRC corrections for Network-controlled repeaters | ZTE Corporation (Rapporteur) |
| R2-2401827 | RIL conclusions for NCR | ZTE Corporation |
| 7.1.2 | Others | |
| R2-2400322 | Restriction of cell list for NCR-MT cell reselection | Samsung |
| R2-2401678 | Restriction of cell list for NCR-MT cell reselection | Samsung |
| R2-2401680 | Restriction of cell list for NCR-MT cell reselection | Samsung |
| R2-2401684 | Restriction of cell list for NCR-MT cell reselection | Samsung |
| R2-2402053 | Restriction of cell list for NCR-MT cell reselection | Samsung |
| 7.2.1 | Organizational | |
| R2-2400007 | LS on UE selection for Ranging_SL (C1-240431; contact: Xiaomi) | CT1 |
| R2-2400027 | LS on the request for specific SL PRS resource characteristic(s)/SL-PRS resource configuration (R1-2312630; contact: Qualcomm) | RAN1 |
| R2-2400038 | LS on LMF involvement in SL-PRS resource allocation (R3-237860; contact: Xiaomi) | RAN3 |
| R2-2400052 | Reply LS on TA validation for LPHAP (R4-2321464; contact: Huawei) | RAN4 |
| R2-2400053 | Response to reply LS on SRS and PRS bandwidth aggregation for positioning (R4-2321545; contact: Ericsson) | RAN4 |
| R2-2400067 | Reply LS on security aspects for Ranging/Sidelink Positioning (S3-235078; contact: Xiaomi) | SA3 |
| R2-2400074 | LS to RAN2/CT WGs on RAN&CT alignment issues (S2-2313889; contact: Xiaomi) | SA2 |
| R2-2400076 | LS on coverage condition for Ranging/Sidelink Positioning (S2-2401383; contact: ZTE) | SA2 |
| R2-2400084 | LS reply on introduction of RAT-Dependent integrity (S2-2401589; contact: CATT) | SA2 |
| R2-2400086 | Reply LS on security aspects for Ranging/Sidelink Positioning (S2-2401651; contact: Sony) | SA2 |
| R2-2400155 | Discussion on LMF involvement in SL-PRS resource allocation | vivo |
| R2-2400206 | LS on confirmation of DL measurements for RedCap and BW | CATT |
| R2-2400281 | Draft Reply LS on LMF involvement in SL-PRS resource allocation | Xiaomi |
| R2-2400282 | Discussion on RAN3 and SA2 LSs for SL positioning | Xiaomi |
| R2-2400338 | Rapporteur CR for MAC spec for R18 positioning | Huawei, HiSilicon |
| R2-2400677 | Discussion on LSs of LMF involvement in SL positioning | ZTE Corporation |
| R2-2400679 | Discussion on SA2 LS on partial coverage | ZTE Corporation |
| R2-2400682 | Draft reply LS on coverage condition for Ranging Sidelink Positioning | ZTE Corporation |
| R2-2400967 | Support of SRS pre-configuration in RAN3 | Samsung |
| R2-2401082 | Corrections to TS 37.355 (rapporteur's CR) | CATT |
| R2-2401236 | Request for specific SL-PRS resource characteristic(s)/SL-PRS resource configuration [LS in R2-2400027 (R1-2312630)] | Qualcomm Incorporated |
| R2-2401239 | LPP ASN.1 Review File and Consolidated RIL List | Qualcomm Incorporated |
| R2-2401241 | LPP Class 0 Issues | Qualcomm Incorporated |
| R2-2401318 | RRC Positioning Corrections based upon RILs | Ericsson |
| R2-2401465 | Discussion on reply to SA3 LS on security aspects for Ranging Sidelink Positioning | OPPO |
| R2-2401629 | Reply LS on coverage condition for Ranging/Sidelink Positioning | RAN2 |
| R2-2401630 | Corrections to the MAC spec for R18 positioning | Huawei, HiSilicon |
| R2-2401631 | Corrections to TS 37.355 (rapporteur's CR) | CATT |
| R2-2401632 | RRC Positioning Corrections based upon RILs | Ericsson |
| R2-2401643 | Reply LS on SL-PRS resource allocation | RAN2 |
| R2-2401644 | Questions on RAN1 parameter list | RAN2 |
| R2-2401699 | Reply LS on MAC agreements for SL Positioning (R1-2401552; contact: Intel) | RAN1 |
| R2-2401701 | LS on bandwidth aggregation for positioning (R1-2401708; contact: ZTE) | RAN1 |
| R2-2401714 | LS on the bandwidth used in measurements for positioning of RedCap UEs (R1-2401801; contact: Ericsson) | RAN1 |
| R2-2401717 | LS on higher layer parameters for SL Positioning (R1-2401827; contact: Intel, Qualcomm) | RAN1 |
| R2-2401777 | [Post125][409][POS] 38.331 Rel-18 positioning CR (Ericsson) | Ericsson |
| R2-2401803 | Updates on measurement report mapping for Positioning Enhancements WI (R4-2403363; contact: Huawei) | RAN4 |
| R2-2401809 | LS on SRS and PRS bandwidth aggregation feature for positioning (R4-2403654; contact: Ericsson) | RAN4 |
| R2-2401821 | Reply LS on UE selection for Ranging_SL (S2-2403682; contact: Qualcomm) | SA2 |
| R2-2401830 | [Post125][408][POS] 37.355 Rel-18 positioning CR (CATT) | CATT |
| 7.2.2 | Stage 2 | |
| R2-2400683 | Discussion on stage-2 procedure corrections | ZTE Corporation |
| R2-2400987 | Solution for some key RIL issues impacting stage-2 | Nokia, Nokia Shanghai Bell |
| R2-2401009 | Discussion on correction for TS 38.305 | InterDigital, Inc. |
| R2-2401243 | Miscellaneous Stage 2 Corrections and Alignments | Qualcomm Incorporated |
| R2-2401568 | Miscellaneous Stage 2 Corrections and Alignments | Qualcomm Incorporated |
| 7.2.3 | SLPP corrections | |
| R2-2400154 | [V003][V001] Discussion on SLPP issues | vivo |
| R2-2400284 | Discussion on SLPP open issues | Xiaomi |
| R2-2400285 | Draft CR 38.355 for SLPP capability | Xiaomi |
| R2-2400336 | Discussion on the remaining issues for SLPP | Huawei, HiSilicon |
| R2-2400359 | [POST124][POS] [TS 38.355] Open Issue list and ASN.1 review | Intel Corporation |
| R2-2400360 | Miscellaneous corrections to SLPP specification | Intel Corporation |
| R2-2400361 | Further considerations on SLPP open issues | Intel Corporation |
| R2-2400583 | Open issues in SLPP | Nokia, Nokia Shanghai Bell |
| R2-2400625 | Discussion on open issues in SLPP | Lenovo |
| R2-2400681 | Discussion on SLPP corrections | ZTE Corporation |
| R2-2400943 | [A006], [Rapp004] SLPP Issues | Apple |
| R2-2400944 | Miscellaneous SLPP corrections | Apple |
| R2-2400961 | Remaining issues on SLPP | Samsung |
| R2-2401107 | Open issues on SLPP specification | LG Electronics Inc. |
| R2-2401244 | [RILs Q001, Q002] Common SL-PRS Request/Provide Assistance Data | Qualcomm Incorporated |
| R2-2401245 | [RILs Q004, Q006] SL-RTT Request/Provide Location Information | Qualcomm Incorporated |
| R2-2401246 | [RILs Q003, Q005, Q012] Various SLPP Corrections | Qualcomm Incorporated |
| R2-2401464 | Discussion on including the server UE positioning method in the discovery message | OPPO |
| R2-2401466 | Discussion on reporting multiple Rx-Tx measurement for the sidelink positioning | OPPO |
| R2-2401526 | Draft CR 38.355 for SLPP capability | Xiaomi |
| R2-2401559 | Draft LS to RAN1 on decisions on SLPP | Intel |
| R2-2401633 | [AT125][409][POS] Remaining SLPP issues (Intel) | Intel Corporation |
| R2-2401641 | CR 38.355 for SLPP capability | Xiaomi |
| R2-2401650 | Miscellaneous corrections to SLPP specification | Intel Corporation |
| R2-2401919 | LS to RAN1 on decisions on SLPP | RAN2 |
| 7.2.4 | LPP corrections | |
| R2-2400203 | [C001] Correction to need code of the IE NR-PeriodicControlParam | CATT |
| R2-2400303 | Open issues for LPP spec | Spreadtrum Communications |
| R2-2400345 | [H022-H024] Discussion on measurement report for CA positioning | Huawei, HiSilicon |
| R2-2400346 | [H015] Discussion on per error source Integrity service paremeters | Huawei, HiSilicon |
| R2-2400362 | Further considerations on LPP open issues | Intel Corporation |
| R2-2400425 | [M001] Definition of PRU in 37.355 | MediaTek Inc. |
| R2-2400678 | Discussion on Rel-18 corrections in LPP | ZTE Corporation |
| R2-2400713 | LPP Maintenance issues | Lenovo |
| R2-2400942 | [A001], [A002], [A003], [A006] LPP Issues | Apple |
| R2-2400988 | Solution for some key RIL issues impacting LPP | Nokia, Nokia Shanghai Bell |
| R2-2401010 | Discussion on correction for LPP | InterDigital, Inc. |
| R2-2401083 | [V300] Correction on integrityBeamInfoBounds | CATT, vivo |
| R2-2401163 | [H003][Z001] Discussion on the CA positioning resource set indication | Huawei, HiSilicon |
| R2-2401182 | [H015] Discussion on per error source integrity parameters | Huawei, HiSilicon |
| R2-2401184 | [H006] Discussion on the TRP ID for CA POS | Huawei, HiSilicon |
| R2-2401186 | [H001] Discussion on PRU modeling | Huawei, HiSilicon |
| R2-2401247 | LPP Open Issue: DL-PRS–DRX Alignment | Qualcomm Incorporated |
| R2-2401248 | LPP Open Issue: PRU Operation | Qualcomm Incorporated |
| R2-2401249 | [RILs Q018, Q026, Q027] Integrity Assistance Data Request/Support | Qualcomm Incorporated, CATT |
| R2-2401250 | [RILs Q019, Q024, Q028] Clarification of field description for aggregated and hopping measurement results | Qualcomm Incorporated |
| R2-2401310 | RIL E100 LPP and E013 SLPP capability for hybrid positioning | Ericsson |
| R2-2401311 | RIL E101 Discussion on Optional or conditional for field nr-DL-PRS-MeasurementTimeWindowsConfig | Ericsson |
| R2-2401312 | RIL E103 Missing RedCap capability for RRC Connected mode | Ericsson |
| R2-2401313 | Discussion related to LPP RILs E001-E003 and Q033 [LocalCoords] | Ericsson |
| R2-2401314 | Discussions related to LPP RIL E004 on Integrity Bounds | Ericsson |
| R2-2401321 | Addressing sidelink open issues and various LS | Ericsson |
| R2-2401325 | Addressing Remaining Integrity Issues | Ericsson |
| R2-2401444 | [POST124][POS][37355] Open Issue list and RIL | CATT |
| R2-2401496 | LPP RIL list for Rel-18 Positioning | CATT |
| 7.2.5 | RRC corrections | |
| R2-2400156 | Discussion on RRC open issues for POS | vivo |
| R2-2400202 | Discussion on the release of SRS configuration | CATT, Samsung, LG Electronics Inc, xiaomi |
| R2-2400205 | [C414] Activation of SP SRS when configured with validity area | CATT |
| R2-2400340 | [H571][H901][H902] Discussion on SIB23 | Huawei, HiSilicon |
| R2-2400341 | [H573] [H574] [H575] Discussion on SRS with validity area | Huawei, HiSilicon |
| R2-2400342 | [H577] Discussion on UAI for SL positoning | Huawei, HiSilicon |
| R2-2400343 | [H604] Discussion on the exceptional pool for SL positoning | Huawei, HiSilicon |
| R2-2400344 | [H903] Disucssion on collision handlig for SL-PRS | Huawei, HiSilicon |
| R2-2400347 | [H581][H590] Discusison on SUI for SL positioning | Huawei, HiSilicon |
| R2-2400676 | Discussion on LPHAP, SL pos and BW aggregation in RRC | ZTE Corporation |
| R2-2400968 | [S207][S205][Z156] Remaining issues on RRC | Samsung |
| R2-2400970 | Discussion on the validity timer for the SRS with validity area | Beijing Xiaomi Electronics |
| R2-2400989 | Solution for some key RIL issues impacting RRC | Nokia, Nokia Shanghai Bell |
| R2-2401252 | Remaining issues for pre-configured SRS | Qualcomm Incorporated |
| R2-2401317 | Open issues list For RRC Positioning | Ericsson |
| R2-2401365 | RRC Positioning RIL List | Ericsson |
| 7.2.6 | MAC corrections | |
| R2-2400157 | Discussion on remaining MAC open issues of SL positioning | vivo |
| R2-2400204 | Discussion on the remaining issues on bandwidth aggregation for SRS | CATT |
| R2-2400229 | Discussion on MAC open issue [CA#02] for NR Pos | Lenovo |
| R2-2400261 | Discussion on MAC issues for SL positioning | InterDigital, Inc. |
| R2-2400283 | Discussion on positioning MAC open issues | Xiaomi |
| R2-2400337 | Discussion on the remaining issues for R18 positioning MAC spec | Huawei, HiSilicon |
| R2-2400363 | Further considerations on MAC open issues | Intel Corporation |
| R2-2400680 | Discussion on SL pos and BW in MAC | ZTE Corporation |
| R2-2400716 | SL Positioning MAC Maintenance issues | Lenovo |
| R2-2400884 | Remaining issues on SL-PRS transmission | ASUSTeK |
| R2-2400885 | Discussion and correction regarding SL PRS resource request | ASUSTeK |
| R2-2400969 | Remaining issues on MAC | Samsung |
| R2-2401056 | MAC related remaining issues of SL positioning | Sharp |
| R2-2401108 | Open issues on MAC specification | LG Electronics Inc. |
| R2-2401189 | MAC spec open issue list for R18 POS | Huawei, HiSilicon |
| R2-2401253 | MAC Open Issue CA#02: MAC CE for activation/deactivation of aggregated SP SRS for positioning | Qualcomm Incorporated |
| R2-2401322 | Addressing MAC open issues | Ericsson |
| R2-2401467 | Discussion on Sidelink positioning MAC open issues | OPPO |
| R2-2401612 | Summary for [offline 401] MAC spec issues for R18 positioning | Huawei, HiSilicon |
| R2-2401912 | LS on positioning MAC agreements | RAN2 |
| 7.2.7 | UE capabilities | |
| R2-2400364 | Further considerations on UE capability open issues | Intel Corporation |
| R2-2400915 | draft 38.306 CR for Positioning Capability | Xiaomi |
| R2-2400953 | Draft 38.331 CR for positioning capability | Xiaomi |
| R2-2400954 | draft LPP CR for Positioning Capability | Xiaomi |
| R2-2400958 | Open issue list for Rel-18 positioning capability | Xiaomi |
| R2-2401527 | draft 38.306 CR for Positioning Capability | Xiaomi |
| R2-2401528 | Draft 38.331 CR for positioning capability | Xiaomi |
| R2-2401529 | draft LPP CR for Positioning Capability | Xiaomi |
| R2-2401638 | draft 38.306 CR for Positioning Capability | Xiaomi |
| R2-2401639 | Draft 38.331 CR for positioning capability | Xiaomi |
| R2-2401640 | LPP CR for positioning UE capability | Xiaomi |
| R2-2402052 | LPP CR for positioning UE capability | Xiaomi |
| 7.2.8 | Corrections to other specifications | |
| R2-2400339 | Discussion on the remaining issues for idle mode procedure | Huawei, HiSilicon |
| R2-2400365 | Further considerations on TS 38.304 open issues | Intel Corporation |
| R2-2401324 | Addressing SL cell reselection open issues | Ericsson |
| R2-2401688 | Correction to IDLE mode procedure for R18 positioning | Huawei, HiSilicon |
| 7.3.1 | Organizational | |
| R2-2400014 | LS on Cell DTX/DRX operations for sTRP (R1- 2312409; contact: Intel) | RAN1 |
| R2-2400216 | LS on new definitions of energy efficiency and energy consumption eDRX (S5-240816; contact: Huawei) | SA5 |
| R2-2400308 | Network energy savings for NR miscellaneous RRC CR | Huawei, HiSilicon |
| R2-2401457 | Network energy savings for NR miscellaneous MAC CR | InterDigital |
| R2-2401715 | LS on Network Energy Savings (R1-2401810; contact: Intel, Huawei) | RAN1 |
| R2-2401877 | Network energy savings for NR miscellaneous RRC CR | Huawei, HiSilicon |
| R2-2401879 | Miscellaneous MAC corrections for network energy savings | InterDigital |
| R2-2401950 | Clarification of cell DTX/DRX operation with TRP | Ericsson |
| R2-2402025 | Miscellaneous MAC corrections for network energy savings | InterDigital |
| R2-2402071 | Network energy savings for NR miscellaneous RRC CR | Huawei, HiSilicon |
| 7.3.2 | User Plane | |
| R2-2400278 | Open issues in MAC | Xiaomi |
| R2-2400304 | Discussion on user plane related issues of NES | Huawei, HiSilicon |
| R2-2400484 | Open issue on the cellDTRX-RNTI monitoring | OPPO |
| R2-2400485 | Correction on the SP CSI reporting | OPPO |
| R2-2400486 | Discussion on remaining issues for the emergency call | OPPO |
| R2-2400608 | Correction on Cell DRX/DTX and SP CSI report in 38.321 | ZTE Corporation, Sanechips |
| R2-2400744 | Open issues on Cell DTX/DRX | Fraunhofer IIS, Fraunhofer HHI |
| R2-2400757 | MAC corrections for cell DTX-DRX | Ericsson |
| R2-2400791 | Open Issues in NES UP | Qualcomm Incorporated |
| R2-2400860 | UE NES-RNTI monitoring behaviour | NEC |
| R2-2400876 | Remaining MAC open issues on NES | Fujitsu |
| R2-2400918 | Remaining issues on alignment between Cell DTX and UE CDRX | Apple, Lenovo, KDDI, OPPO |
| R2-2400920 | User Plane open issues on NES | Apple |
| R2-2400959 | remaining open issues for cell DTRX | vivo |
| R2-2400974 | Remaining issues on NES-RNTI monitoring for Cell DTX/DRX | Nokia, Nokia Shanghai Bell, Vodafone, Samsung |
| R2-2401098 | Discussion on the UP open issues of NES | CATT |
| R2-2401114 | Remaining issues on cell DTX and cell DRX mechanism | LG Electronics Inc. |
| R2-2401147 | Discussion on NES and TP to TS 38.300 | CMCC |
| R2-2401148 | Discussion on NES and TP to TS 38.321 | CMCC |
| R2-2401199 | Coexistence of Cell DTX/DRX and RACH-less LTM/handover | Sharp |
| R2-2401218 | Remaining open issues for Rel-18 NES | MediaTek Inc. |
| R2-2401362 | MAC Open Issues on Cell DTX/DRX | Samsung |
| R2-2401455 | Remaining issues on Cell DTX/DRX | InterDigital |
| R2-2401864 | Summary of [AT125][007][NES] NES-RNTI monitoring | InterDigital |
| 7.3.3 | Control Plane corrections | |
| R2-2400191 | UE capability for SSB-less Scell | Huawei, HiSilicon |
| R2-2400279 | [RIL-X203]Open issues on inter-band SSB-less SCell | Xiaomi |
| R2-2400280 | [RIL-X201]Cell selection after NES CHO failure | Xiaomi |
| R2-2400305 | [H044] Discussion on Cell DTX/DRX UE capability relation to NES cell barring | Huawei, HiSilicon |
| R2-2400306 | [H724] optionality of Need M fields in cell DTX/DRX config | Huawei, HiSilicon |
| R2-2400307 | NES WI RIL list | Huawei, HiSilicon |
| R2-2400495 | Cell Switch off and NES Mode Indication | Lenovo, Motorola Mobility, Continental Automotive, Nokia, Nokia Shanghai Bell, BT Plc, Vodafone, Sony, Google, CEWiT |
| R2-2400508 | Cell Switch off and NES Mode Indication | Lenovo, Motorola Mobility, Continental Automotive, Nokia, Nokia Shanghai Bell, BT Plc, Vodafone, Sony, Google, CEWiT, Deutsche Telekom |
| R2-2400563 | Cell Switch off and NES Mode Indication | Lenovo, Motorola Mobility, Continental Automotive, Nokia, Nokia Shanghai Bell, BT Plc, Vodafone, Sony, Google, CEWiT, Deutsche Telekom, Ericsson |
| R2-2400590 | Open issue: mTRP and NES | Ericsson |
| R2-2400606 | Consideration on NES cell barring and cell DTX/DRX UE capability | ZTE Corporation, Sanechips |
| R2-2400607 | Correction on cell DTX/DRX in 38.300 | ZTE Corporation, Sanechips |
| R2-2400746 | Remaining Issues on Cell Selection and Re-Selection for NES | Fraunhofer IIS, Fraunhofer HHI |
| R2-2400756 | Description of UE support for NW DTX-DRX | Ericsson |
| R2-2400792 | Open Issues in NES CP | Qualcomm Incorporated |
| R2-2400861 | Cell barring for NES Cell DTX, Cell DRX, or both | NEC |
| R2-2400895 | Discussion on remaining open issue of cell barring for NES | LG Electronics Inc. |
| R2-2400919 | Control plane open issues on NES | Apple |
| R2-2400960 | cell barring for UEs capable of cell DTRX | vivo |
| R2-2401099 | Consideration on the cell barring issue for NES | CATT |
| R2-2401100 | Discussion on Cell DTX/DRX UE capability | CATT |
| R2-2401115 | [L007] RRC indication of initial activation status of cell DTX and cell DRX | LG Electronics Inc. |
| R2-2401169 | CHO for NES and RLM | Nokia, Nokia Shanghai Bell |
| R2-2401170 | [NES RRC Open Issue 1] Barring and UE capabilities | Nokia, Nokia Shanghai Bell |
| R2-2401171 | [N042] On RIL for Network Energy Savings | Nokia, Nokia Shanghai Bell |
| R2-2401221 | NES CP Corrections | Samsung |
| R2-2401333 | Cell DTX and DRX operation during RRC Resume | Samsung |
| R2-2401361 | Cell Switch off and NES Mode Indication | Lenovo, Motorola Mobility, Continental Automotive, Nokia, Nokia Shanghai Bell, BT Plc, Vodafone, Sony, Google, CEWiT, Deutsche Telekom, Ericsson, Samsung |
| R2-2401456 | Remaining issues in Control Plane for NES | InterDigital |
| R2-2401564 | Correction on NES UE capabilities to 38306 | vivo, CATT |
| R2-2401566 | Corrections for Network Energy Savings in 38.304 | Apple |
| R2-2401868 | Report of [AT125][007][NES] Cell DTX/DRX configuration in RRC_INACTIVE | Huawei |
| R2-2401878 | NES WI RIL list | Huawei, HiSilicon |
| 7.4.1 | Maintenance | |
| R2-2400015 | Reply LS on L1 measurements for LTM (R1-2312443; contact: Ericsson) | RAN1 |
| R2-2401713 | LS on TCI state after cell switch command for LTM ( R1-2401785; contact: Fujitsu) | RAN1 |
| R2-2401807 | LS on R18 mobility - Improvement on SCell/SCG setup delay (R4-2403549; contact: Apple) | RAN4 |
| 7.4.1.1 | Organizational | |
| R2-2400029 | LS on MAC CE to activate/deactivate semi-persistent PUCCH report for LTM (R1-2312642; contact: Fujitsu) | RAN1 |
| R2-2400039 | Reply LS on subsequent CPAC (R3-237949; contact: ZTE) | RAN3 |
| R2-2400050 | Reply LS on L1 measurements for LTM (R4-2321388; contact: Ericsson) | RAN4 |
| R2-2400051 | LS on n-TimingAdvanceOffset for PDCCH order RACH (R4-2321389; contact: Huawei) | RAN4 |
| R2-2400271 | Discussion on RAN1 LS on Activation/Deactivation of SP PUCCH for LTM | CATT, Fujitsu |
| R2-2401382 | Miscellaneous corrections on further mobility enhancements in NR | Ericsson |
| R2-2401385 | RILs conclusions for feMob | Ericsson |
| R2-2401386 | Discussion on RILs conclusion Mobillity | Ericsson |
| R2-2401575 | Miscellaneous corrections on further mobility enhancements in NR | Ericsson |
| R2-2401693 | RILs conclusions for feMob | Ericsson |
| R2-2401814 | Reply LS on MAC CE to activate/deactivate semi-persistent PUCCH report for LTM | RAN2 |
| R2-2401954 | [Draft] Reply LS on MAC CE to activate/deactivate semi-persistent PUCCH report for LTM | Fujitsu |
| R2-2401958 | Reply LS on n-TimingAdvanceOffset for PDCCH order RACH | RAN2 |
| 7.4.1.2 | Stage-2 Corrections | |
| R2-2400140 | Discussion on stage-2 corrections for Rel-18 LTM | Huawei, HiSilicon |
| R2-2400310 | Miscellaneous corrections for NR further mobility enhancements in TS 37.340 | ZTE Corporation, Sanechips |
| R2-2400543 | Miscellaneous Corrections to LTM | Mediatek Inc., vivo |
| R2-2400576 | TA acquisition related open issues | Rakuten Mobile, Inc |
| R2-2400577 | Delayed Resource Reservation for inter gNB-DU LTM | Rakuten Mobile, Inc |
| R2-2400578 | Remaining open issues of L1/L2 Triggered Mobility | Rakuten Mobile, Inc |
| R2-2401061 | TA validity check for UE based TA measurement | Fujitsu |
| R2-2401140 | Discussion on S-CPAC and TP for TS 37.340 | CMCC |
| R2-2401381 | Stage-2 corrections for Rel-18 mobility enhancements | Ericsson, Vodafone |
| R2-2401470 | Stage-2 corrections for SCPAC | OPPO |
| R2-2401610 | Stage-2 Corrections to LTM | Mediatek Inc., vivo |
| R2-2401687 | Miscellaneous corrections for NR further mobility enhancements in TS 37.340 | ZTE Corporation (Rapporteur), Sanechips |
| 7.4.1.3 | RRC Corrections | |
| R2-2400494 | Considerations on CHO with SCG(s) and Subsequent CPAC | Samsung R&D Institute UK |
| 7.4.1.3.1 | L1L2 Triggered Mobility | |
| R2-2400165 | Tolerable key stream re-use | Xiaomi |
| R2-2400184 | Coexistence of LTM with other features | Xiaomi |
| R2-2400197 | Handling keystream reuse at recovery | Samsung Electronics Co., Ltd |
| R2-2400209 | Discussion on key stream reuse during LTM fast recovery | Transsion Holdings |
| R2-2400221 | [B100] SCG LTM with fast MCG link recovery | Lenovo, Samsung |
| R2-2400222 | UE measured TA and No L2 reset in coexistence case of L3 handover and LTM | Lenovo |
| R2-2400275 | Issue on the association between CSI-RS and SSB of the LTM candidate cell | CATT |
| R2-2400311 | Discussion on coexistence of LTM and other features | ZTE Corporation, Sanechips |
| R2-2400312 | Consideration on remaining issues for LTM | ZTE Corporation, Sanechips |
| R2-2400356 | RRC signaling related TCI state configurations | Panasonic |
| R2-2400391 | [FeMob][Issue 4] Handling of key stream re-used in case of fast LTM recovery | Intel Corporation |
| R2-2400441 | Coexistence of LTM and other features | vivo |
| R2-2400442 | Discussion on the key stream reuse issue for LTM | vivo |
| R2-2400443 | Discussion on the impact of s-Measure on L1 measurement | vivo |
| R2-2400444 | [V121][V122]Unknown target configuration ID in LTM cell switch command | vivo |
| R2-2400468 | Discussion on LTM remaining issues | LG Electronics |
| R2-2400492 | Discussion on remaining issues for LTM | Samsung |
| R2-2400496 | Analysis of Keystream reuse issue | Lenovo, Motorola Mobility |
| R2-2400509 | Remaining issue for LTM | NTTDOCOMO, INC. |
| R2-2400574 | Discussion on coexistence of LTM with other features | China Telecom |
| R2-2400603 | Discussion on security issue of LTM | NEC |
| R2-2400668 | On Reference Configuration in Rel-18 LTM | Nokia, Nokia Shanghai Bell |
| R2-2400795 | Views on fast cell recovery during LTM failures | Panasonic |
| R2-2400796 | PDCP keystream handling for LTM fast recovery | Panasonic |
| R2-2400806 | On the interworking of LTM with L3 Mobility and Dual Connectivity | Nokia, Nokia Shanghai Bell |
| R2-2400807 | On the cell switch aspects in LTM | Nokia, Nokia Shanghai Bell |
| R2-2400812 | RRC Remaining issues on LTM | Huawei, HiSilicon |
| R2-2400814 | Reply LS on n-TimingAdvanceOffset for PDCCH order RACH | Huawei, HiSilicon |
| R2-2400815 | Early RACH for inter-DU LTM | Huawei, HiSilicon |
| R2-2400816 | [H018][H035] LTM configuration | Huawei, HiSilicon |
| R2-2400817 | [H020] SRB L2 behaviour | Huawei, HiSilicon |
| R2-2400835 | Coexistence of LTM and other features | Interdigital, Inc. |
| R2-2400839 | Security issues during LTM failure recovery | Interdigital, Inc. |
| R2-2400840 | Draft LS on Key Stream Reuse during fast LTM recovery | Interdigital, Inc. |
| R2-2400872 | Solutions for keystream reuse issue caused by fast LTM recovery | Fujitsu |
| R2-2400956 | Coexistence of LTM and Other Mobility Procedures and Features | MediaTek Inc. |
| R2-2401054 | Coexistence of LTM and other features | Sharp |
| R2-2401062 | Considerations on LTM related open issues | Fujitsu |
| R2-2401063 | [F015] Default value of n-TimingAdvanceOffset in IE EarlyUL-SyncConfig | Fujitsu |
| R2-2401123 | Keystream Reuse Issue in LTM Fast Recovery | MediaTek Inc. |
| R2-2401179 | Discussion on fast recovery and co-existence with other features | Qualcomm Incorporated |
| R2-2401242 | Correction on 38.331 for LTM | Langbo |
| R2-2401284 | Discussion on keystream reuse issue at LTM fast recovery | NTT DOCOMO, INC. |
| R2-2401364 | Discussion on LTM candidate ID value range and related issue (G001) | Google Inc. |
| R2-2401379 | Co-existence of LTM with other features | Ericsson |
| R2-2401383 | Clarify presence of securityConfig in case of LTM [E068] | Ericsson |
| R2-2401384 | Corrections on UE-based TA measurements [C113, Z051, B105, B202, C114, M002, B106, L005, Z030, C116, A702, Z059] | Ericsson |
| R2-2401468 | Discussion on RRC issues of LTM | OPPO |
| R2-2401471 | Discussion on cross-feature issues for LTM | OPPO |
| R2-2401926 | Summary of [AT125][510][feMob] LTM RRC issues | Ericsson |
| 7.4.1.3.2 | Subsequent CPAC | |
| R2-2400185 | Open issues of L2 reset for subsequent CPAC | Xiaomi |
| R2-2400210 | Discussion on remaining issues in Subsequent CPAC | Transsion Holdings |
| R2-2400272 | [C109] MCG configuration handling upon Subsequent CPAC | CATT |
| R2-2400273 | [C123] Execution Condition of Subsequent CPAC | CATT |
| R2-2400274 | Open Issue on L2 Reset for Subsequent CPAC | CATT |
| R2-2400313 | Consideration on remaining issues for subsequent CPAC | ZTE Corporation, Sanechips |
| R2-2400395 | Remaining issues in Subsequent CPAC | Qualcomm Incorporated |
| R2-2400445 | [V136] Execution condition for subsequent CPA | vivo |
| R2-2400446 | [V135] Subsequent CPAC condition handling after execution | vivo |
| R2-2400491 | [S792] SRB3 release during SCPAC and LTM | Samsung |
| R2-2400604 | Remaining issue of subsequent CPAC including [E072] | NEC |
| R2-2400788 | Open issues for subsequent CPAC | Ericsson |
| R2-2400789 | Further issues for subsequent CPAC | Ericsson |
| R2-2400836 | Subsequent CPAC L2 reset | Interdigital, Inc. |
| R2-2401014 | [C123][E072][V136] open issues related to SCPAC | LG Electronics |
| R2-2401037 | On remaining issues for SCPAC | Nokia, Nokia Shanghai Bell |
| R2-2401055 | L2 reset in case of subsequent CPAC | Sharp |
| R2-2401185 | [C123][V136][V135] Execution condition update for subsequent CPAC | MediaTek Inc. |
| R2-2401472 | Discussion on the open issues for subsequent CPAC | OPPO |
| R2-2401571 | LS on SCPAC inter node agreements | RAN2 |
| R2-2401880 | Report of [AT125][504][feMob] SCPAC inter-node issues (Ericsson) | Ericsson |
| R2-2401930 | Report of [AT125][502][feMob] SCPAC execution conditions(CATT) | CATT |
| R2-2401953 | TP of L2 reset | OPPO |
| 7.4.1.3.3 | CHO including target MCG and candidate SCGs for CPC CPA in NR-DC | |
| R2-2400669 | On the Remaining Issues for CHO with CPC in Rel-18 | Nokia, Nokia Shanghai Bell |
| 7.4.1.4 | MAC Corrections | |
| R2-2400139 | Miscellaneous corrections for further mobility enhancements in MAC | Huawei, HiSilicon |
| R2-2400141 | MAC remaining issues on LTM | Huawei, HiSilicon |
| R2-2400164 | Remaining MAC issues for LTM | Xiaomi |
| R2-2400196 | MAC corrections for LTM | Samsung Electronics Co., Ltd |
| R2-2400276 | Issues on deactivation of TCI states of LTM candidate cell | CATT |
| R2-2400319 | Need of RSRP checking for CFRA | NEC |
| R2-2400320 | MAC CE to activate-deactivate semi-persistent PUCCH report for LTM | NEC |
| R2-2400447 | Discussion on MAC open issues for LTM | vivo |
| R2-2400482 | On serving cell TA issues with UE TA measurement | Futurewei |
| R2-2400483 | TS38.321 TP on source cell TA update for UE based TA measurement | Futurewei |
| R2-2400575 | Discussion on MAC CE to activate/deactivate semi-persistent PUCCH report for LTM | China Telecom |
| R2-2400837 | MAC CE to activate/deactivate semi-persistent PUCCH | Interdigital, Inc. |
| R2-2400879 | Discussion MAC CE for LTM | NTPU |
| R2-2400880 | Discussion on remaining issues of RACH-less LTM cell switch | NEC |
| R2-2400886 | Discussion on fallback RACH for LTM | ASUSTeK |
| R2-2400887 | Discussion on LTM candidate configuration for different CGs | ASUSTeK |
| R2-2400888 | Discussion on support for multi-TA candidate Cell in LTM | ASUSTeK |
| R2-2400889 | Discussion on early UL synchronization in LTM | ASUSTeK |
| R2-2400957 | LTM MAC Open Issues | MediaTek Inc. |
| R2-2401044 | Considerations On Remaining MAC Issues For LTM | ZTE Corporation, Sanechips |
| R2-2401045 | Miscellneous On MAC Spec for LTM | ZTE Corporation, Sanechips |
| R2-2401064 | Corrections to TS 38.321 on LTM | Fujitsu |
| R2-2401085 | Correction on PUSCH transmission during RACH-less LTM cell switch | LG Electronics Inc. |
| R2-2401086 | Consideration on MAC open issues for LTM | LG Electronics Inc. |
| R2-2401191 | Ongoing Random Access procedure handling for LTM | Langbo |
| R2-2401194 | PREAMBLE_POWER_RAMPING_COUNTER increment condition for LTM | Langbo |
| R2-2401195 | PREAMBLE_POWER_RAMPING_COUNTER reset condition for LTM | Langbo |
| R2-2401204 | Support of L1/L2 controlled LTM CSI reporting | Samsung |
| R2-2401380 | MAC remaining issues for LTM | Ericsson |
| R2-2401469 | Discussion on MAC issues for LTM | OPPO |
| R2-2401477 | Discussion on MAC Issues for LTM | CATT |
| R2-2401689 | Miscellaneous corrections for further mobility enhancements in MAC | Huawei, HiSilicon |
| R2-2401828 | Postponed issue list for LTM MAC corrections | Huawei, HiSilicon |
| R2-2401924 | Summary of [AT125][509][feMob] MAC offline | Huawei, HiSilicon |
| 7.4.1.5 | UE capabilities | |
| R2-2400385 | Report of [Post124][561][feMob] UE capability (Intel) | Intel Corporation |
| R2-2400386 | Draft 331 CR for UE capability for feMob | Intel Corporation |
| R2-2400387 | Draft 306 CR for UE capability for feMob | Intel Corporation |
| R2-2400392 | Discussion on remaining open issues on UE capability for feMob | Intel Corporation |
| R2-2401812 | Draft 331 CR for UE capability for feMob | Intel Corporation |
| R2-2401813 | Draft 306 CR for UE capability for feMob | Intel Corporation |
| 7.4.2 | WI Open Parts | |
| R2-2400166 | Discussion on eEMR SCell setup delay | vivo |
| R2-2400186 | Discussion on improvement to SCell/SCG setup delay | Xiaomi |
| R2-2400277 | Discussion on Improvement to SCell SCG Setup Delay | CATT |
| R2-2400314 | Discussion on SCell/SCG setup delay improvement | ZTE Corporation, Sanechips |
| R2-2400321 | Improvement to SCell-SCG setup delay | NEC |
| R2-2400790 | Discussion on early measurements enhancements | Ericsson |
| R2-2400813 | Remaining issues on EMR | Huawei, HiSilicon |
| R2-2400838 | Improvement on Scell/SCG setup/resume delay | Interdigital, Inc. |
| R2-2401149 | Discussion on fast SCell/SCG setup delay improvement | CMCC |
| R2-2401162 | Discussion on WI objective #7 extension | MediaTek Inc. |
| R2-2401172 | [Post123bis][551][feMob] eEMR SCell setup delay (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2401231 | Enhancements of early measurement report for fast CA/DC setup | LG Electronics Inc. |
| R2-2401473 | Discussion on improvement to SCell/SCG setup delay | OPPO |
| R2-2401933 | eEMR and IMR CR | Nokia, Nokia Shanghai Bell |
| R2-2401990 | eEMR and IMR CR | Nokia, Nokia Shanghai Bell |
| 7.5.1 | Organizational | |
| R2-2400069 | Reply LS on provisioning separate DL and UL PDU Set QoS Parameters to NG-RAN (S2-2313689; contact: Qualcomm) | SA2 |
| R2-2400077 | Reply LS on XR awareness and LS on uplink PDU Set (S2-2401405; contact: vivo) | SA2 |
| R2-2400079 | Reply LS on out of order reception for the end PDU of PDU Set/Data Burst (S2-2401841; contact: CMCC) | SA2 |
| R2-2400088 | LS on out of order reception for the end PDU of PDU Set/Data Burst (S4-231955; contact: Huawei) | SA4 |
| R2-2400145 | Corrections to TS 38.321 (rapporteur's CR) | Qualcomm Incorporated |
| R2-2400393 | 38.306 draftCR of UE Capability for XR | Intel Corporation |
| R2-2400394 | 38.331 draftCR of UE Capability for XR | Intel Corporation |
| R2-2400448 | Discussion on UL PDU set based QoS handling based on SA2 LS | vivo |
| R2-2400476 | XR Agreements | Nokia (Rapporteur) |
| R2-2400477 | Miscellaneous XR corrections | Nokia (Rapporteur) |
| R2-2400868 | XR Stage 2 Open Issues | Nokia (Rapporteur) |
| R2-2401535 | Miscellaneous XR corrections | Nokia (Rapporteur) |
| R2-2401580 | Correction to TS 38.321 | Qualcomm Incorporated (rapporteur) |
| R2-2401601 | Update to UE’s capabilities for Rel-18 XR | Intel Corporation |
| R2-2401602 | Update to UE’s capabilities for Rel-18 XR | Intel Corporation |
| R2-2401692 | Data volume calculation for DSR when associated with at least two RLC entities | LG Electronics Inc. (Rapporteur) |
| R2-2401843 | Miscellaneous XR corrections | Nokia (Rapporteur) |
| R2-2401985 | Data volume calculation for DSR when associated with at least two RLC entities | LG Electronics Inc. (Rapporteur) |
| R2-2402038 | Correction to TS 38.321 | Qualcomm Incorporated (rapporteur) |
| 7.5.2 | RRC corrections | |
| R2-2400225 | Corrections for burst arrival time issue | Lenovo |
| R2-2400388 | [RIL I052] Initial/default behaviour of PDU Set identification | Intel Corporation |
| R2-2400389 | PSI Identification defined in UL traffic info. of UAI [Issue 4 on open issue list to 38.300, RIL: H399] | Intel Corporation, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson, Apple |
| R2-2400436 | UE capabilities for XR | Xiaomi |
| R2-2400437 | [X101] Absence of traffic information of QoS flow | Xiaomi |
| R2-2400438 | [X102] Decoupling of BAT and XR assistance information | Xiaomi |
| R2-2400449 | [V152] Discussion on UAI reporting per QoS flow | vivo |
| R2-2400547 | [F011] Corrections on the DRX configurations | Fujitsu |
| R2-2400560 | Capability/UAI and RRC Issues | NEC |
| R2-2400561 | BSR Specific Issues | NEC |
| R2-2401181 | [X091] Unclear UL timing of BAT | Xiaomi Communications |
| R2-2401203 | Remaining issues on DRX for XR | China Telecom |
| R2-2401413 | Rapporteur RRC CR for XR | Huawei, HiSilicon |
| R2-2401414 | XR RIL resolutions | Huawei, HiSilicon |
| R2-2401415 | Discussion on BAT definition [H551] | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO |
| R2-2401419 | Discussion for the UE capability related to DRX enhancements | Huawei, HiSilicon |
| R2-2401422 | Discussion on the configuration for UTO-UCI [H552][H553][I136] | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Xiaomi, Intel Corporation |
| R2-2401569 | RRC corrections for XR | Huawei, HiSilicon |
| R2-2401695 | XR RIL resolutions | Huawei, HiSilicon |
| 7.5.3.1 | BSR enhancements for XR | |
| R2-2400105 | Leftover Issues on BSR | CATT |
| R2-2400146 | Correction to padding BSR with the refined BSR table | Qualcomm Incorporated |
| R2-2400226 | Corrections for padding BSR for refined BSR | Lenovo |
| R2-2400327 | Discussing on issues on BSRDSR and proposed TP to MAC | Xiaomi Communications |
| R2-2400450 | Discussion on remaining issues and corrections for BSR | vivo |
| R2-2400487 | Open issues on the Padding BSR | OPPO |
| R2-2400549 | Refined Long BSR as the padding BSR | Fujitsu |
| R2-2400665 | MAC BS table correction for Rel-18 XR | Futurewei |
| R2-2400750 | Consideration on the BSR specific open issues | ZTE Corporation, Sanechips |
| R2-2400873 | Remaining issues on BSR | DENSO CORPORATION |
| R2-2400917 | Corrections on padding BSR for EoDB indication | Samsung |
| R2-2400924 | Remaining Issues on BSR for Rel-18 XR | Apple |
| R2-2400975 | Remaining issues on BSR enhancements | Nokia, Nokia Shanghai Bell |
| R2-2400982 | Remaining open issue on BSR | LG Electronics Inc. |
| R2-2401151 | Discussion on remaining open issue for BSR | CMCC |
| R2-2401366 | Discussion on BSR trigger | Ericsson, Qualcomm, Apple, Intel Corporation |
| 7.5.3.2 | DSRDSR specific corrections/open issues | |
| R2-2400106 | Further Discussion on DSR | CATT |
| R2-2400147 | Discussion on cancelation of DSR MAC CE | Qualcomm Incorporated, Apple, MediaTek |
| R2-2400291 | Corrections for DSR procedure | Samsung |
| R2-2400299 | Discussion on XR open issues | Spreadtrum Communications |
| R2-2400358 | Remaining issues of DSR enhancement for XR | NEC Corporation |
| R2-2400369 | Corrections to the DSR procedure | Lenovo |
| R2-2400451 | Discussion on remaining issues and corrections for DSR | vivo |
| R2-2400488 | Discussion on the SR triggering for DSR | OPPO |
| R2-2400489 | The impact on DSR due to intra-UE prioritization | OPPO |
| R2-2400550 | Discussions on DSR | Fujitsu |
| R2-2400751 | Consideration on the DSR specific open issues | ZTE Corporation, Sanechips |
| R2-2400874 | Remaining issues on DSR | DENSO CORPORATION |
| R2-2400890 | Discussion on SR configuration for DSR MAC CE | ASUSTeK |
| R2-2400925 | Remaining Issues on DSR for Rel-18 XR | Apple |
| R2-2400976 | Remaining issues on DSR enhancements | Nokia, Nokia Shanghai Bell |
| R2-2400983 | Remaining open issue on DSR | LG Electronics Inc. |
| R2-2401417 | Discussion on triggerring and reporting DSR | Huawei, HiSilicon |
| 7.5.3.3 | PDCP and discard operation | |
| R2-2400325 | PSI-Based discard Activation-Deactivation MAC CE and proposed TP | Xiaomi Communications, Qualcomm Incorporated |
| R2-2400326 | Remaining issues on PDCP impact of DSR and proposed TP | Xiaomi Communications, Futurewei, CMCC, Huawei, HiSilicon |
| R2-2400370 | PDCP corrections and open issues | Lenovo |
| R2-2400390 | PDCP SN Gap Notification | Intel Corporation |
| R2-2400439 | PDCP open issue: Data volume calculation for DSR when associated with at least two RLC entities | LG Electronics |
| R2-2400440 | Need for PDCP discard notifications to receiving PDCP entity | LG Electronics, Xiaomi, NEC, Oppo, Samsung |
| R2-2400452 | Discussion on PDCP discard notification to receiver | vivo |
| R2-2400453 | Discussion on remaining issues and corrections for discard | vivo |
| R2-2400478 | PDCP Discarding Issues | Nokia, Nokia Shanghai Bell |
| R2-2400480 | Corrections and Considerations for PDCP and Discard Operation | Samsung |
| R2-2400562 | Delay Critical Data and PSI-based Discard | NEC |
| R2-2400666 | Miscellaneous PDCP corrections for Rel-18 XR | Futurewei |
| R2-2400748 | PDCP discard notification for XR | ZTE Corporation, Sanechips, Futurewei, Canon |
| R2-2400797 | Indication of PDCP SN Gaps | Ericsson |
| R2-2400834 | Discussion on SN gap issue | CANON Research Centre France, CATT |
| R2-2400845 | PDCP and discard operation | InterDigital |
| R2-2400891 | Clarification on PDU Set discard handling when QoS flow remapping | ASUSTeK |
| R2-2400902 | PDCP discard operation | MediaTek Inc. |
| R2-2400926 | Views on PDCP Discard Notification for Rel-18 XR | Apple |
| R2-2401326 | On PDCP Discard Notification for XR | Google Inc. |
| R2-2401367 | Discussion on Delay-critical PDCP data | Ericsson |
| R2-2401418 | Initial state for PSI-based SDU discard [H559] | Huawei, HiSilicon, Ericsson |
| R2-2401420 | Discussion on receiving window update for PDCP discard | Huawei, HiSilicon |
| R2-2401443 | Discussion on PDCP discard notification | NTT DOCOMO INC.. |
| R2-2401448 | Remaining issues related to PDCP discard | Sony |
| R2-2401837 | PDCP SN Gap Reporting | Intel Corporation, CATT, Fujitsu, Ericsson, Canon, Apple, InterDigital, Futurewei, Huawei, HiSilicon, ZTE, vivo, NTT DOCOMO, MediaTek Inc., Nokia, Nokia Shanghai Bell |
| R2-2401863 | SN Gap analysis | LG Electronics |
| 7.5.3.4 | Others | |
| R2-2400107 | Issues on Configured Grant and Non-integer DRX Cycle | CATT |
| R2-2400108 | Definition Correction for PSDB and PSER in TS38.300 | CATT |
| R2-2400148 | Correction to the determination of unused CG occasions | Qualcomm Incorporated, Apple, MediaTek |
| R2-2400357 | Remaining issues on non-integer DRX cycle | NEC Corporation |
| R2-2400378 | Other MAC corrections for XR | Samsung |
| R2-2400490 | Open issues on the CG enhancement | OPPO |
| R2-2400548 | Corrections on the DRX operations | Fujitsu |
| R2-2400749 | Non-Integer C-DRX cycle related issues | ZTE Corporation, Sanechips |
| R2-2400896 | Consideration on remaining issues in XR | LG Electronics Inc. |
| R2-2400927 | Views on Unused and Invalid CG Occasions | Apple |
| R2-2401210 | Open issues on DRX for XR | China Telecom |
| R2-2401329 | Remaining issues for XR enhancement | Google Inc. |
| R2-2401405 | R18 XR UTO-UCI correction | Ericsson |
| R2-2401416 | DRX_SFN_COUNTER initialization issue for SFN wrap-around [H556] | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE Corporation, Sanechips, LGE |
| R2-2401421 | Discussion on the UTO-UCI MAC procedures | Huawei, HiSilicon |
| 7.6.1 | Organizational | |
| R2-2400005 | LS on UE Location Information for NB-IoT NTN (C1-239363; contact: Ericsson) | CT1 |
| R2-2400022 | LS on Rel-18 RAN1 UE features list for LTE after RAN1#115 (R1-2312571; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2400034 | LS on improved GNSS operations in Rel-18 IoT NTN (R1-2312696; contact: MediaTek) | RAN1 |
| R2-2400071 | Reply LS on misalignment between PTW and Coverage Window (S2-2313795; contact: Huawei) | SA2 |
| R2-2400692 | Corrections to IOT NTN | Huawei, HiSilicon |
| R2-2400693 | IOT NTN ASN1 RIL List | Huawei, HiSilicon |
| R2-2400694 | RRC open issue list | Huawei, HiSilicon |
| R2-2401567 | Discussion on the remaining issues of IoT NTN MAC CR | MediaTek Inc. |
| R2-2401595 | Corrections to IOT NTN | Huawei, HiSilicon |
| R2-2401596 | Corrections to IoT NTN | MediaTek |
| R2-2401708 | LS on improved GNSS operations in Rel-18 IoT NTN (R1-2401754; contact: MediaTek) | RAN1 |
| R2-2401716 | LS on Rel-18 RAN1 UE features list for LTE after RAN1#116 (R1-2401824; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2401823 | Reply LS on UE Location Information for NB-IoT NTN (S2-2403851; contact: Qualcomm) | SA2 |
| R2-2401925 | LS on improved GNSS operations in Rel-18 IoT NTN (R1-2401754; contact: MediaTek) | RAN1 |
| R2-2402034 | Updated IoT NTN ASN1 RIL List | Huawei, HiSilicon |
| 7.6.2 | Stage 2 corrections | |
| R2-2400715 | GNSS validity duration and duration X | PANASONIC |
| R2-2401127 | Discussion on stage 2 open issue UE behavior at failed GNSS acquisition | Nokia, Nokia Shanghai Bell |
| R2-2401280 | Correction to Stage 2 on IoT NTN | Huawei, HiSilicon |
| R2-2401402 | R18 IoT NTN corrections to stage 2 | Ericsson |
| R2-2401460 | Correction to Stage 2 on IoT NTN | Huawei, HiSilicon |
| R2-2401461 | Correction to Stage 2 on IoT NTN | Huawei, HiSilicon |
| R2-2401463 | Miscellaneous corrections for IoT NTN | Samsung |
| R2-2401514 | Correction to Stage 2 on IoT NTN | Huawei, HiSilicon |
| R2-2401581 | Summary of [AT125][301][IoT-NTN Enh] Flagged RILs | Huawei |
| R2-2401584 | [AT125][304][IoT NTN Enh] Stage 2 corrections (Ericsson) | Ericsson |
| R2-2401600 | Corrections to stage 2 for IoT NTN | Ericsson, Huawei, Samsung |
| 7.6.3 | RRC Corrections | |
| R2-2400117 | Discussion on CHO within UL Transmission Extention | vivo |
| R2-2400118 | Remaining Issues on Location Based CHO | vivo |
| R2-2400119 | [V502] Remaining Issues on Autonomous GNSS Measurement | vivo |
| R2-2400193 | [H001] Clarification for CondEvent D1 | Huawei, HiSilicon |
| R2-2400194 | [H002] UE capability differentiation for GSO and NGSO | Huawei, HiSilicon |
| R2-2400253 | [C601] TP on CHO recovery for time-based CHO in Rel-18 IoT NTN | CATT |
| R2-2400254 | [C603] Corrections on location-based CHO for earth moving cell | CATT |
| R2-2400255 | [C600] Remaining issues on UL transmission extension timer handling after GNSS expiry | CATT |
| R2-2400287 | Discussion on IOT NTN RRC open issues | Xiaomi |
| R2-2400429 | Discussions of Remaining RRC Corrections in IoT-NTN | MediaTek Inc. |
| R2-2400499 | Open Issues on the GNSS Operation Enhancements | Google Inc. |
| R2-2400502 | Corrections Relevant to the RRC Connection Release | Google Inc. |
| R2-2400846 | RRC Corrections and discussion on RILs | Samsung |
| R2-2400856 | Discussion on RIL Q631 | Qualcomm Incorporated |
| R2-2400859 | Leftover issue on UE Autonomous release in moving cell | Qualcomm Incorporated |
| R2-2401004 | Discussion on open issues for discontinuous coverage | OPPO |
| R2-2401128 | On RIL [N015] Location-based CHO evaluation in duration X | Nokia, Nokia Shanghai Bell |
| R2-2401139 | Discussion on IoT-NTN and TP for TS 36.331 | CMCC |
| R2-2401232 | RRC corrections on GNSS enhancements for IoT NTN (RILZ364, Z365) | ZTE Corporation, Sanechips |
| R2-2401234 | RRC corrections on other aspects for IoT NTN (RILZ367) | ZTE Corporation, Sanechips |
| R2-2401294 | Remaining issues on GNSS fix | Apple |
| R2-2401494 | [S061][S063] Correction on SatelliteInfo frequency lists | Samsung |
| 7.6.4 | MAC corrections | |
| R2-2400120 | Remaining Issues on UL Transmission Extention | vivo |
| R2-2400121 | Cancellation of Triggered GNSS Validity Duration Reporting | vivo |
| R2-2400211 | Discussion on remaining issues on HARQ enhancements | Transsion Holdings |
| R2-2400286 | Discussion on IOT NTN MAC open issues | Xiaomi |
| R2-2400428 | Discussion on MAC corrections on Rel-18 IoT-NTN | MediaTek Inc. |
| R2-2400847 | On uplink transmission extension and related RILs | Samsung |
| R2-2400857 | Open issues on out-of-date GNSS fix | Qualcomm Incorporated |
| R2-2400858 | Open issue: DRX inactivity timer start | Qualcomm Incorporated |
| R2-2401001 | Discussion on HARQ enhancement for IoT NTN | OPPO |
| R2-2401002 | Discussion on remaining open issues on GNSS enhancement | OPPO |
| R2-2401003 | DRAFT LS on GNSS validity duration | OPPO |
| R2-2401129 | Correction to 36.321 on GNSS validity duration reporting | Nokia, Nokia Shanghai Bell |
| R2-2401130 | Discussion on MAC open issues for IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2401138 | Discussion on IoT-NTN and TP for TS 36.321 | CMCC |
| R2-2401235 | Remaining issues of MAC spec for IoT NTN | ZTE Corporation, Sanechips |
| R2-2401279 | Correction on GNSS validity duration reporting | Huawei, HiSilicon |
| R2-2401295 | New MAC CE for UL transmission extension Y | Apple |
| R2-2401401 | R18 IoT NTN GNSS extension | Ericsson |
| R2-2401459 | Correction on GNSS validity duration reporting | Huawei, HiSilicon |
| R2-2401515 | Correction on GNSS validity duration reporting | Huawei, HiSilicon |
| 7.6.5 | Corrections to other specs | |
| R2-2400252 | Corrections on location based cell reselection for IoT NTN in TS 36.304 | CATT |
| R2-2400848 | On GNSS measurements during C-DRX | Samsung |
| R2-2401041 | Clarifications for GNSS measurement related UE capabilities | Nokia, Nokia Shanghai Bell |
| R2-2401043 | Miscellanious corrections for IoT-NTN | Nokia Solutions & Networks (I) |
| R2-2401238 | Corrections on UE capability for IoT NTN | ZTE Corporation, Sanechips |
| R2-2401278 | Remaining issues on discontinous coverage | Huawei, HiSilicon |
| R2-2401597 | Introduction of IoT-NTN Enhancements | Nokia, Nokia Shanghai Bell |
| R2-2401598 | Update on IoT NTN UE capabilities | Qualcomm Inc. |
| R2-2401829 | Update on IoT NTN UE capabilities | Qualcomm Inc. |
| R2-2402059 | Update on IoT NTN UE capabilities | Qualcomm Inc. |
| 7.7.1 | Organizational | |
| R2-2400033 | LS on NR-NTN TP for TS 38.300 (R1-2312681; contact: Thales | RAN1 |
| R2-2400036 | LS on OAM requirements for UE location verification (R3-238056; contact: CATT) | RAN3 |
| R2-2400045 | Reply LS on NW verified UE location failure during cell change (R3-238024; contact: Qualcomm) | RAN3 |
| R2-2400054 | LS on Handover Times for NTN UEs with mechanically steered beams in FR2-NTN (R4-2321576; contact: Nokia) | RAN4 |
| R2-2400061 | LS on NTN VSAT capability (R4-2321975; contact: ZTE) | RAN4 |
| R2-2400062 | LS on UE capability to support DMRS bundling for GSO and NGSO (R4-2321976; contact: Ericsson) | RAN4 |
| R2-2400068 | Reply LS on the service requirement of restricting satellite access RAT type (S1-233296; contact: Apple) | SA1 |
| R2-2400085 | Response to “Reply LS on the service requirement of restricting satellite access RAT type” (S2-2401650; contact: Vodafone) | SA2 |
| R2-2400534 | Consideration on VSAT support requested in R4-2321975 | ZTE Corporation, Sanechips |
| R2-2400609 | Miscellaneous Corrections in 38.304 | ZTE Corporation, Sanechips |
| R2-2400711 | RIL List on 37.355 for NR NTN | CATT |
| R2-2400712 | Correction on NR NTN in TS 37.355 | CATT |
| R2-2401410 | Rapporteur input R18 NR NTN RRC | Ericsson |
| R2-2401411 | Rapporteur input R18 NR NTN RRC RIL | Ericsson |
| R2-2401449 | Draft LS response on Handover delay in FR2 NTN with mechanically steered beams | Nokia |
| R2-2401582 | Summary of [AT125][302][NR NTN Enh] Flagged RILs | Ericsson |
| R2-2401585 | [AT125][305][NR NTN Enh] VSAT support (ZTE) | ZTE corporation, Sanechips |
| R2-2401589 | Corrections to Rel-18 NR NTN enhacements | Ericsson |
| R2-2401591 | Miscellaneous Corrections for NTN in 38.304 | ZTE Corporation, Sanechips |
| R2-2401592 | Correction on NR NTN in TS 37.355 | CATT |
| R2-2401593 | Updates to UE capabilities for Rel-18 NR NTN Enh | Intel |
| R2-2401594 | Updates to UE capabilities for Rel-18 NR NTN Enh | Intel |
| R2-2401707 | Reply LS on Satellite Switch with Resync (R1-2401748; contact: Apple) | RAN1 |
| R2-2401805 | Reply LS on RAN2 agreements for satellite switch with resync (R4-2403493; contact: Apple) | RAN4 |
| 7.7.2 | Stage 2 corrections | |
| R2-2400771 | 38.300 corrections for network verified UE location | Nokia, Nokia Shanghai Bell |
| R2-2400772 | On combining CHO and RACH-less | Nokia, Nokia Shanghai Bell |
| R2-2401282 | Correction to Stage 2 on NTN mobility | Huawei, HiSilicon |
| R2-2401403 | Corrections to stage 2 for NR NTN R18 | Ericsson |
| R2-2401462 | Miscellaneous Stage 2 corrections for NR NTN | Samsung |
| R2-2401513 | Correction to Stage 2 on NTN mobility | Huawei, HiSilicon |
| R2-2401583 | 38.300 NR NTN Corrections | THALES (Rapporteur), Ericsson, Huawei, HiSilicon, Mediatek, Intel, Nokia, Nokia Shanghai Bell, Samsung |
| R2-2401599 | 38.300 NR NTN Corrections | THALES (Rapporteur), Ericsson, Huawei, HiSilicon, Mediatek, Intel, Nokia, Nokia Shanghai Bell, Samsung |
| R2-2402051 | 38.300 NR NTN Corrections | THALES (Rapporteur), Ericsson, Huawei, HiSilicon, Intel, Mediatek, Nokia, Nokia Shanghai Bell, Samsung |
| 7.7.3 | RRC corrections | |
| R2-2400122 | [V503] Remaining Issues on Location Based CHO for Moving Cell | vivo |
| R2-2400123 | Remaining Issues on Satellite Switch with Re-sync | vivo |
| R2-2400124 | [V507] Clarification on RACH-less CG Periodicity | vivo |
| R2-2400182 | Consideration of remaining open issues of NTN | China Telecom |
| R2-2400195 | [H063] RACH-based satellite switching with re-sync | Huawei, HiSilicon, CATT, CMCC |
| R2-2400248 | Discussion on leftover open issues of TS 38.331 | CATT |
| R2-2400249 | [C604] [C622] On parameter applicability to CG RACH-less HO in NR NTN | CATT |
| R2-2400250 | [C619] On serving cell configuration for EMC CHO | CATT |
| R2-2400251 | Discussion on Remaining Open Issue for Unchanged PCI Mechanism (H001) | CATT, Huawei, HiSilicon, CMCC |
| R2-2400309 | [H009] NTN coverage enhancement implementation in RRC | Huawei, HiSilicon |
| R2-2400481 | The remaining issues of satellite switch of re-sync | TCL |
| R2-2400497 | Discussion on open issue for NTN CHO | LG Electronics France |
| R2-2400498 | Discussion on open issue for satellite swithcing with re-sync | LG Electronics France |
| R2-2400500 | Open Issues on the Satellite Switch with Resynchronization | Google Inc. |
| R2-2400501 | Provision of the TN PLMN ID in an NTN Cell | Google Inc. |
| R2-2400535 | [RILH005,H400] Consideration on location-based CHO remaining issues | ZTE Corporation, Sanechips |
| R2-2400536 | Inclusion of NTN-Config for PCI unchanged | ZTE Corporation, Sanechips |
| R2-2400537 | Inclusion of Msg4 ACK repetition parameters | ZTE Corporation, Sanechips |
| R2-2400538 | [RILH001]Discussion on the switch timing for soft-switch case | ZTE Corporation, Sanechips |
| R2-2400670 | Further Thoughts on CHO in EMC [C606] | Nokia, Nokia Shanghai Bell |
| R2-2400695 | [H001] Discussion on unchanged PCI | Huawei, HiSilicon |
| R2-2400696 | [H005][H004][H008] Event D2 for earth-moving cell | Huawei, HiSilicon |
| R2-2400697 | [H792] Measurement results reporting for unchanged PCI cell | Huawei, HiSilicon |
| R2-2400698 | [H010][O602][C603] Discussion on ssb-TimeOffset | Huawei, HiSilicon |
| R2-2400699 | [H791] SMTC for measuring unchanged PCI cell | Huawei, HiSilicon |
| R2-2400700 | [H790] Applicable events for unchanged PCI cell | Huawei, HiSilicon |
| R2-2400701 | [H062] SIB19 acquisition after satellite switching | Huawei, HiSilicon |
| R2-2400702 | [H400] Correction to CondEvent D2 | Huawei, HiSilicon |
| R2-2400703 | CHO configuration in satellite switching | Huawei, HiSilicon |
| R2-2400802 | RRC corrections for NTN | InterDigital |
| R2-2400808 | Issues on condEventD2 and RACH-less HO | Samsung |
| R2-2400809 | Issues on satellite switch with PCI unchanged and RIL S481 | Samsung |
| R2-2400852 | RIL Q571 and H792 on issue of serving satellite change | Qualcomm Incorporated |
| R2-2400853 | DL sync and switch time in Satellite switch with re-sync | Qualcomm Incorporated |
| R2-2400855 | RACH-less satellite switch with resync | Qualcomm Incorporated |
| R2-2400869 | Discussion on configuration of ntn-cg-RACH-less-RetransmissionTimer | LG Electronics Inc. |
| R2-2400892 | [K003] Discussion on satellite switch triggering | ASUSTeK |
| R2-2400937 | Open issues on satellite switch with unchanged PCI | Apple |
| R2-2400938 | Open issues on NR NTN Enhancements | Apple |
| R2-2400992 | [H015] Start and stop condition of T430 | Huawei, HiSilicon |
| R2-2401005 | [O600] Discusssion on TN cell broadcasting NTN info | OPPO |
| R2-2401006 | [O601] Discussion on location-based CHO for earth moving cells | OPPO |
| R2-2401007 | [O602] Discussion on unchanged PCI | OPPO |
| R2-2401084 | [C606] Further discussion on CHO in EMC | CATT, Thales, vivo, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ITL, OPPO |
| R2-2401134 | Considerations on left issues on EMC CHO | CMCC |
| R2-2401135 | Considerations on left issues on PCI unchanged | CMCC |
| R2-2401183 | On first UL transmission for unchanged PCI RIL H001 | Nokia, Nokia Shanghai Bell |
| R2-2401256 | Open issues on location based CHO | ITL |
| R2-2401258 | Open issues on satellite switching with re-sync | ITL |
| R2-2401393 | Remaining issues on NR NTN Enhancements | Sequans Communications |
| R2-2401400 | Remaining issue on soft satellite switch with re-sync | Ericsson |
| 7.7.4 | MAC corrections | |
| R2-2400125 | Remaining Issues on PUCCH Repetition | vivo |
| R2-2400803 | MAC corrections for NTN | InterDigital |
| R2-2400810 | Corrections on NTN MAC issues | Samsung |
| R2-2400871 | Indication for HARQ feedback for RACH-less handover | LG Electronics Inc. |
| R2-2400881 | Discussion on corrections for RACH-less handover without retransmission timer | NEC |
| R2-2400882 | Discussion on remaining issues of RACH-less handover for NTN | NEC |
| R2-2400939 | Clarification on UE operation upon TATimer expiry during RACH-less HO | Apple |
| R2-2401281 | Discussion on MAC behaviours related to RACH-less HO and unchanged PCI | Huawei, HiSilicon |
| R2-2401590 | Corrections to Rel-18 NTN enhancements | InterDigital |
| R2-2402033 | Input on remaining proposals not related to RACH-less HO | InterDigital (Rapporteur) |
| 7.7.5 | Corrections to other specs | |
| R2-2400587 | Discussion on the measurement rules for cell re-selection | ETRI |
| R2-2400854 | RIL Q638 on FR2 in NTN | Qualcomm Incorporated |
| R2-2401000 | Discussion on PUCCH enhancement for Msg4 HARQ-ACK in NR NTN | OPPO |
| R2-2401277 | Open issues on GNSS enhancements | Huawei, HiSilicon |
| R2-2401404 | Remaining issue on VSAT UEs | Ericsson |
| R2-2401409 | Remaining issue on switch procedure for satellite switch with re-sync | Ericsson |
| 7.8.1 | Organizational | |
| R2-2400044 | LS on RAN3 progress for UAV flight path information handling and A2X service support (R3-238019; contact: Ericsson) | RAN3 |
| R2-2400564 | Correction for SL resource pool usage for BRID/DAA transmission | Samsung |
| R2-2400611 | Clarification for the capability of NumberOfTriggeringCells | Huawei, HiSilicon, Ericsson |
| R2-2400671 | Work Item Agreements for Uncrewed Aerial Vehicles in Rel-18 | Nokia, Nokia Shanghai Bell |
| R2-2400672 | Corrections to NR Support for Uncrewed Aerial Vehicles | Nokia, Nokia Shanghai Bell |
| R2-2400673 | Corrections to Enhanced LTE Support for Uncrewed Aerial Vehicles. | Nokia, Nokia Shanghai Bell |
| R2-2400830 | Corrections for NR Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2400831 | Corrections for Enhanced LTE Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2400832 | NR UAV: Proposed resolutions to ASN.1 review and other open issues | Qualcomm Incorporated |
| R2-2400833 | LTE eUAV: Proposed resolutions to ASN.1 review and other open issues | Qualcomm Incorporated |
| R2-2401605 | Corrections for NR Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2401606 | Corrections for Enhanced LTE Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2401607 | NR UAV: Status of ASN.1 review issues after RAN2#125 | Qualcomm Incorporated |
| R2-2401608 | LTE eUAV: Status of ASN.1 review issues after RAN2#125 | Qualcomm Incorporated |
| R2-2401609 | UE capability corrections for NR Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2401817 | LS Reply on Aerial Pmax values (R4-2403830; contact: Nokia) | RAN4 |
| R2-2401870 | Corrections to NR Support for Uncrewed Aerial Vehicles | Nokia, Nokia Shanghai Bell |
| R2-2401871 | Corrections to Enhanced LTE Support for Uncrewed Aerial Vehicles. | Nokia, Nokia Shanghai Bell |
| R2-2401873 | Correction for SL resource pool usage for BRID/DAA transmission | Samsung |
| R2-2401955 | Corrections to NR Support for Uncrewed Aerial Vehicles | Nokia, Nokia Shanghai Bell |
| 7.8.2 | Measurement reporting for mobility and interference control | |
| R2-2400173 | Discussion on single measurement report triggering for multiple events of same type | vivo |
| R2-2400366 | Measurement Reporting Enhancements | NEC |
| R2-2400506 | Discussion on Measurement report enhancement for NR UAV | LG Uplus |
| R2-2400589 | H746 H747 J064 E048 J061 E144 | Ericsson |
| R2-2400602 | Altitude dependent NumberOfTriggeringCells [H744] [H746] [H747] | Huawei, HiSilicon, Ericsson |
| R2-2400674 | On Some of the Most Interesting RILs for Rel-18 UAVs: [E129], [E144], [H744], [V824] | Nokia, Nokia Shanghai Bell |
| R2-2400990 | [Z076] Correction on application of altitude based SSB-ToMeasure | ZTE Corporation, Sanechips |
| R2-2400991 | [Z077] Correction on application of simulMultiTriggerSingleMeasReport | ZTE Corporation, Sanechips |
| R2-2401212 | Discussion on Measurement Reporting Enhancements | China Telecom |
| 7.8.3 | Flight path reporting | |
| R2-2400367 | Remaining issues on Flight Path Reporting | NEC |
| R2-2400612 | Discussion on flight path report | Huawei, HiSilicon |
| R2-2400798 | E129, Flight Path Reporting | Ericsson |
| R2-2401059 | Discussion related to L004 | LG Electronics |
| 7.8.4 | Other | |
| R2-2400113 | Discussion on open issues for UAV UE capabilities | CATT |
| R2-2400172 | Discussion on the granularity of UE capability on sidelink A2X service | vivo |
| R2-2400565 | [S171] SIB12 acquisiton for A2X communication | Samsung |
| R2-2400613 | Remaining issues for NR UAV | Huawei, HiSilicon |
| R2-2400675 | Resolving Remaining Open Issues for Rel-18 UAV capabilities | Nokia, Nokia Shanghai Bell |
| R2-2400825 | Remaining aspects of PC5-based A2X and UE capabilities | Qualcomm Incorporated |
| R2-2401060 | Open Issue related to simultaneous MR | LG Electronics |
| R2-2401202 | Correction on resource pools selection for A2X communication | Sharp |
| R2-2401213 | On Flight Path Updating and UAV UE Capabilities | China Telecom |
| R2-2401230 | Correction on Sidelink procedure for A2X communication | Samsung |
| R2-2401399 | Resource selection for BRID and DAA | Beijing Xiaomi Mobile Software |
| 7.9.1 | Organizational | |
| R2-2400072 | Reply LS on L2ID and User Info for L2 based U2U (S2-2313796; contact: LGE) | SA2 |
| R2-2400073 | Reply LS on handling of location information in multi-path operation (S2-2313800; contact: LGE) | SA2 |
| R2-2400505 | Discussion on L2ID and User Info for L2 based U2U | LG Electronics Inc. |
| R2-2400507 | Reply LS on L2ID and User Info for L2 based U2U relay (reply to R2-2400072; contact: LGE) | LG Electronics Inc. |
| R2-2400566 | Correction on 38.306 for SL Relay UE capability | Samsung |
| R2-2400567 | Correction on 38.331 for SL Relay UE capability | Samsung |
| R2-2400633 | Corrections for NR sidelink relay enhancements | OPPO |
| R2-2400768 | U2U relay selection and reselection | Nokia, Nokia Shanghai Bell |
| R2-2400804 | Correction on 38.304 for SL Relays | Ericsson |
| R2-2400949 | Discussion on Reply LS on L2ID and User Info for L2 U2U | Apple |
| R2-2401155 | Remaining issues on RRC for U2U relay | Qualcomm Incorporated |
| R2-2401156 | Remote UE ID discussion for U2U relay Local ID assignment | Qualcomm Incorporated, Ericsson, MediaTek Inc, InterDigital |
| R2-2401157 | Reply LS on L2ID and User Info for L2 based U2U relay (reply to R2-2400072; contact: Qualcomm) | Qualcomm Incorporated |
| R2-2401615 | WA on L2ID and user info association | Qualcomm |
| R2-2401616 | [DRAFT] LS on U2U relay selection | Nokia |
| R2-2401647 | Corrections for NR sidelink relay enhancements | OPPO |
| R2-2401648 | Correction on 38.306 for SL Relay UE capability | Samsung |
| R2-2401649 | Correction on 38.331 for SL Relay UE capability | Samsung |
| R2-2401916 | LS on U2U relay selection | RAN2 |
| R2-2401918 | Reply LS to SA2 on L2ID and user info | RAN2 |
| 7.9.2 | Stage 2 corrections | |
| R2-2400101 | Correction on R18 SL Relay | CATT |
| R2-2400400 | Correction to 38.300 on Relay enhancement | Xiaomi |
| R2-2400403 | Stage-2 Corrections for SL relay enhancements | Huawei, HiSilicon |
| R2-2400504 | Corrections to 38.300 for Rel-18 SL Relay (rapporteur’s CR) | LG Electronics Inc. |
| R2-2400579 | Stage-2 correction on SL relay | Samsung |
| R2-2400636 | Discussion on stage-2 corrections | OPPO |
| R2-2400689 | Corrections to 38.300 for SL relay | ZTE, Sanechips |
| R2-2401142 | TP to TS 38.300 on SL relay enhancement | CMCC |
| R2-2401450 | Stage-2 Corrections for SL relay enhancements | Huawei, HiSilicon |
| R2-2401476 | Discussion on stage 2 correction for SL relay | ZTE Corporation, Sanechips |
| R2-2401636 | Introduction of NR sidelink relay enhancements | LG Electronics (Rapporteur) |
| R2-2402039 | Introduction of NR sidelink relay enhancements | LG Electronics (Rapporteur) |
| R2-2402040 | Introduction of NR sidelink relay enhancements | LG Electronics (Rapporteur) |
| 7.9.3 | RRC corrections | |
| R2-2400102 | Leftover Issues on Multi-path and U2U Relay | CATT |
| R2-2400134 | Discussion on remaining CP issues for U2U relay | NEC Corporation |
| R2-2400135 | Discussion on remaining CP issues for MP relaying | NEC |
| R2-2400178 | Discussion on RRC open issue of service continuity | China Telecom |
| R2-2400179 | Discussion on RRC open issue of U2U relay | China Telecom |
| R2-2400180 | Discussion on RRC open issue of multi-path | China Telecom |
| R2-2400223 | [B107] [B110] TP on IndirectPathFailureInformation message | Lenovo |
| R2-2400224 | [B109] TP on NotificationMessageSidelink message for U2U | Lenovo |
| R2-2400228 | [B113] TP on T390 in MP scenario | Lenovo |
| R2-2400302 | Open issues for multi-path relaying | Spreadtrum Communications |
| R2-2400379 | RRC issues on MP of SL relay | Samsung |
| R2-2400399 | [H696, O424, H656] Correction on T421 stop condition | Xiaomi |
| R2-2400404 | Remaining stage-3 issues for multi-path operation and U2U relay | Huawei, HiSilicon |
| R2-2400410 | [H656][H695][H696] T421 stop condition for MP remote UE | Huawei, HiSilicon |
| R2-2400411 | [H658][H690] Configuring radio bearer associated with N3C indirect path | Huawei, HiSilicon |
| R2-2400412 | [H660][H669][H673][H693]Clarification of SRAP configuration and local ID/ bearer ID addition/modificaiton/release for U2U relay | Huawei, HiSilicon |
| R2-2400413 | [H662] PC5 unicast link handling for MP operation during RRC re-establishment procedure | Huawei, HiSilicon |
| R2-2400414 | [H065] PC5 link maintainence or release for direct path addition/modification/release procedures | Huawei, HiSilicon |
| R2-2400415 | [H064] QoS infomation and bearer mapping for U2U relay | Huawei, HiSilicon |
| R2-2400416 | [H668][H679] [O408]PC5 RLC channel handling including E2E failure case in U2U relay | Huawei, HiSilicon, OPPO, Vivo |
| R2-2400417 | [H066] Relay UE indication for supporting of PC5-RRC trigger in MP | Huawei, HiSilicon |
| R2-2400418 | [H670] E2E SL DRB handling for U2U relay | Huawei, HiSilicon |
| R2-2400419 | [H811][H692] Conditions for the PC5-RRC trigger | Huawei, HiSilicon |
| R2-2400420 | [H683] Clarification for U2U remote UE threshold condition | Huawei, HiSilicon, Vivo |
| R2-2400421 | [H686] RLC mode indication in L2 U2U relay | Huawei, HiSilicon |
| R2-2400426 | [H659] Network support for non-3GPP multi-path relay | MediaTek Inc. |
| R2-2400469 | Left issues for Multi-path relaying | SHARP Corporation |
| R2-2400493 | Discussion on MP remaining open issues | vivo |
| R2-2400503 | Discussion on the remaining issues for U2U relay | LG Electronics Inc. |
| R2-2400551 | Discussions on RRC | Fujitsu |
| R2-2400569 | [S426] Correction on SL DRB release | Samsung, vivo |
| R2-2400570 | [S427] Correction on SL SRB release | Samsung, vivo |
| R2-2400571 | [S429] Correction for SL RLF handling for L2 U2U relay | Samsung, vivo |
| R2-2400572 | [S432] RSRP thresholds for events X1 and X2 | Samsung |
| R2-2400638 | Discussion on [O400-407, O421] | OPPO, Huawei, vivo |
| R2-2400639 | Discussion on [O419] | OPPO, vivo |
| R2-2400640 | Discussion on [O425] | OPPO |
| R2-2400641 | Discussion on [O414] | OPPO |
| R2-2400642 | Discussion on [O415] | OPPO |
| R2-2400643 | Discussion on [O424] | OPPO |
| R2-2400644 | Discussion on [O418,427,428] | OPPO |
| R2-2400686 | Discussion on remaining issues on U2U relay | ZTE, Sanechips |
| R2-2400687 | Discussion on remaining issues on multi-path relay | ZTE, Sanechips |
| R2-2400735 | Open issue list for Rel-18 SL relay | Huawei, HiSilicon |
| R2-2400736 | RRC RIL issue list for Rel-18 SL relay | Huawei, HiSilicon |
| R2-2400737 | Rapp RRC CR for Rel-18 SL relay enhancement | Huawei, HiSilicon |
| R2-2400742 | [H066] Relay UE indication of supporting PC5-RRC trigger for MP | Huawei, HiSilicon, Qualcomm, Ericsson |
| R2-2400743 | [H674] [H677] Per hop PC5 link release/failure and E2E PC5 link release/failure handling for U2U relay | Huawei, HiSilicon |
| R2-2400765 | RIL N024 - RSRP thresholds for X1, X2, and Y2 events | Nokia, Nokia Shanghai Bell |
| R2-2400766 | RSRP thresholds for U2N relay selection and re-selection | Nokia, Nokia Shanghai Bell |
| R2-2400767 | RIL N025 - QoS split for L2 U2U Relay | Nokia, Nokia Shanghai Bell |
| R2-2400799 | Discussion on Open Issues in 38.331 | Ericsson |
| R2-2400893 | [K001] Corrections to sidelink radio link failure on L2 U2U Relay | ASUSTeK |
| R2-2400894 | [K002] Sidelink UE Capability reporting for L2 U2U Relay | ASUSTeK |
| R2-2400950 | Discussion on local ID release for L2 U2U ([A619]) | Apple |
| R2-2400951 | Discussion on open issues for L2 U2U support ([A606],[A608] etc.) | Apple |
| R2-2400952 | Discussion on direct path add/change/release in MP ([A623] and [A624]) | Apple, InterDigtal Inc |
| R2-2401072 | Use of Direct Path Release for Multipath | InterDigital, Apple, Ericsson, Xiaomi |
| R2-2401074 | Addressing RRC Open Issues for Multipath and Service Continuity | InterDigital |
| R2-2401075 | Addressing RRC Open Issues for U2U Relay | InterDigital |
| R2-2401110 | [Z755] Providing QoS flow to E2E SLRB mapping to relay UE and traffic pattern reporting at relay UE | ZTE, Sanechips |
| R2-2401111 | [Z756] Association of E2E SLRB with PC5 RLC channel at relay UE | ZTE, Sanechips |
| R2-2401117 | RRC remaining issues for U2U relay | Sharp |
| R2-2401143 | TP to TS 38.331 on SL relay enhancement | CMCC |
| R2-2401211 | [J062] Discussion on s-measureConfig for i2i path switching | Sharp |
| R2-2401283 | Discussion on [O417] | OPPO |
| R2-2401285 | Discussion on [O423] | OPPO, Huawei |
| R2-2401394 | [X033] [X251] peer-to-peer direct PC5 trigger for U2U Relay UE selection | Beijing Xiaomi Mobile Software |
| R2-2401396 | [H675] [H676] reception of NotificationMessageSidelink indicating PC5-RLF | Beijing Xiaomi Mobile Software |
| R2-2401446 | Direct path release in multi-path | Sony |
| R2-2401447 | Multipath activation/deactivation | Sony |
| R2-2401486 | [X029/030/031] correction on the relay reselection | Xiaomi |
| R2-2401487 | Discussion on U2U ID reporting | NEC |
| R2-2401617 | [AT125][404][Relay] Remaining prioritized issues on relay RRC (Huawei) | Huawei, HiSilicon |
| R2-2401646 | RRC corrections for Rel-18 SL relay enhancements | Huawei, HiSilicon |
| R2-2402042 | RRC corrections for Rel-18 SL relay enhancements | Huawei, HiSilicon |
| 7.9.4 | SRAP corrections | |
| R2-2400298 | Correction on SRAP for U2U relay | Xiaomi |
| R2-2400405 | SRAP corrections on L2 U2U relay operation | Huawei, HiSilicon |
| R2-2400559 | SRAP – proposals for corrections and related TP | Samsung |
| R2-2400632 | SRAP open issues for R18 sidelink relay | OPPO |
| R2-2400634 | Discussion on left issues for SRAP | OPPO |
| R2-2400688 | Corrections to 38.351 on L2 U2U relay | ZTE, Sanechips |
| R2-2401451 | SRAP corrections on L2 U2U relay operation | Huawei, HiSilicon |
| R2-2401475 | Discussion on SRAP corrections on L2 U2U relay | ZTE Corporation, Sanechips |
| 7.9.5 | MAC corrections | |
| R2-2400103 | Clarification on the Duplication RLC Activation and Deactivation MAC CE | CATT |
| R2-2400401 | Correction to 38.321 on Relay enhancement | Xiaomi |
| R2-2400406 | MAC corrections on multi-path operation and L2 U2U relay | Huawei, HiSilicon |
| R2-2400635 | Discussion on MAC corrections | OPPO |
| R2-2400800 | Discussion on Open Issues in 38.321 | Ericsson |
| R2-2400948 | Miscellaneous MAC Corrections on SL Relay enhancements | Apple (rapporteur) |
| R2-2401452 | MAC corrections on multi-path operation and L2 U2U relay | Huawei, HiSilicon |
| R2-2401634 | Miscellaneous MAC Corrections on SL Relay enhancements | Apple (rapporteur) |
| 7.9.6 | RLC and PDCP corrections | |
| R2-2400104 | Clarification on More than One Leg on Direct Uu Path in Multi-path | CATT |
| R2-2400380 | Remaining issue on PDCP for MP of SL relay | Samsung |
| R2-2400407 | PDCP corrections on L2 U2U relay security | Huawei, HiSilicon |
| R2-2401073 | Rapporteur Corrections to 38.323 for SL Relay | InterDigital |
| R2-2401089 | Clarification for PDCP/RLC with multi-path | Nokia, Nokia Shanghai Bell |
| R2-2401453 | PDCP corrections on L2 U2U relay security | Huawei, HiSilicon |
| R2-2401635 | Miscellaneous Corrections to 38.323 for SL Relay | InterDigital |
| 7.9.7 | UE capabilities | |
| R2-2400402 | Discussion on UE capability of Relay enhancement | Xiaomi |
| R2-2400408 | UE capability corrections for multi-path operation and U2U relay | Huawei, HiSilicon |
| R2-2400568 | Open issue for UE capabilities | Samsung |
| R2-2400573 | Discussion on open issues of UE capability for multi-path relay | China Telecom |
| R2-2400637 | Discussion on UE capability | OPPO |
| R2-2400801 | Discussion on Open Issues in 38.306 | Ericsson |
| R2-2401158 | UE capabilities on MP relay | Qualcomm Incorporated |
| 7.9.8 | Idle mode corrections | |
| R2-2400409 | Idle mode corrections for SL relay | Huawei, HiSilicon |
| 7.10 | IDC enhancements for NR and MR-DC | |
| R2-2400161 | Miscellaneous corrections for IDC | Xiaomi |
| R2-2400162 | IDC RIL list | Xiaomi |
| R2-2401020 | Correction on the IDC Reporting | ZTE Corporation, Sanechips |
| R2-2401525 | Miscellaneous corrections for IDC | Xiaomi |
| R2-2401711 | Correction on the IDC Reporting | ZTE Corporation, Sanechips |
| R2-2401712 | Miscellaneous corrections for IDC | Xiaomi |
| 7.11.1 | Organizational and stage-2 corrections | |
| R2-2400028 | Reply LS on UE Capability of Multicast Reception in RRC_INACTIVE (R1-2312641; contact: vivo) | RAN1 |
| R2-2400266 | Corrections to 38.300 for eMBS | CATT, CBN, China Broadnet |
| R2-2400315 | Correction on TS 38.300 for NR MBS enhancements | THALES |
| R2-2400940 | Miscellaneous corrections to eMBS in MAC | Apple |
| R2-2401150 | Corrections to TS 38.300 for MBS | CMCC |
| R2-2401259 | MBS corrections to Stage 2 | Huawei, vivo, HiSilicon |
| R2-2401262 | MBS Rapporteur CR for RRC | Huawei, HiSilicon |
| R2-2401263 | RIL list for MBS | Huawei, HiSilicon |
| R2-2401298 | Miscellaneous corrections to eMBS in MAC | Apple, Samsung, Qualcomm Incorporated, CATT |
| R2-2401512 | MBS corrections to Stage 2 | Huawei, vivo, HiSilicon |
| R2-2401651 | Corrections to TS 38.300 for MBS | CMCC |
| R2-2401652 | Miscellaneous corrections to eMBS in MAC | Apple, Samsung, Qualcomm Incorporated, CATT |
| R2-2401663 | RIL status for MBS after RAN2#125 | Huawei, HiSilicon |
| R2-2401664 | MBS Rapporteur CR for RRC | Huawei, HiSilicon |
| R2-2401667 | Corrections to TS 38.300 for MBS | CMCC |
| R2-2401668 | Miscellaneous corrections to eMBS in MAC | Apple, Samsung, Qualcomm Incorporated, CATT, ZTE |
| R2-2401669 | Corrections to TS 38.300 for MBS | CMCC |
| R2-2401670 | Corrections to TS 38.300 for MBS | CMCC, Huawei, Qualcomm Incorporated, CATT, NOKIA, Ericsson, vivo, Samsung |
| R2-2402026 | RIL status for MBS after RAN2#125 | Huawei, HiSilicon |
| R2-2402027 | MBS Rapporteur CR for RRC | Huawei, HiSilicon |
| 7.11.2.1 | Control plane corrections | |
| R2-2400109 | Open issues on control plane for multicast reception in RRC_INACTIVE state | TD Tech, Chengdu TD Tech |
| R2-2400227 | [B103] TP on stop monitoring MCCH when entering RRC_CONNECTED state | Lenovo |
| R2-2400263 | [C132] RRC Resume when below the Threshold | CATT, CBN, Huawei, HiSilicon, Xiaomi, China Broadnet |
| R2-2400264 | [C135] Conflict between the legacy MII and Rel-18 MII | CATT, CBN, Huawei, HiSilicon, Samsung, China Broadnet |
| R2-2400373 | [S745] [S746] Optionality of Multicast MCCH Configuration in SIB24 | Samsung |
| R2-2400479 | [W010] Discussion on corrections for RRC resume after RRCReject | NEC |
| R2-2400616 | Discussion about RIL Z657 (on SDAP operation for multicast reception in RRC_INACTIVE) | ZTE, Sanechips |
| R2-2400770 | CP Corrections for Multicast Reception | Samsung |
| R2-2400941 | Clarification on UE operations related to MRB configuration | Apple |
| R2-2401057 | Multicast MRBs Release when switching to RRC_CONNECTED (RIL J003) | Sharp |
| R2-2401088 | RIL issues on multicast | LG Electronics Inc. |
| R2-2401173 | [J001] [C131] [J006] [C140] Control plane details for multicast reception in RRC_INACTIVE state | Nokia, Nokia Shanghai Bell |
| R2-2401175 | [J008][J003][S749] Multicast MRB handling for Inactive state | Nokia, Nokia Shanghai Bell |
| R2-2401264 | [H073] Discussion on how to notify UE of session activation during SDT | Huawei, HiSilicon |
| R2-2401265 | [H074] Discussion on UE behaviour after receiving RRCReject during RRC resume for multicast reception | Huawei, HiSilicon |
| R2-2401359 | RIL E097 MBS quality threshold | Ericsson |
| R2-2401397 | Remaining Issues on UE Triggered RRC Resumption | vivo |
| R2-2401655 | Summary of [AT125][604][eMBS] MRBs handling during state transitions (Sharp) | Sharp |
| 7.11.2.2 | User plane corrections | |
| R2-2400265 | Corrections to 38.321 for eMBS | CATT, CBN, China Broadnet |
| R2-2400556 | Initialization of PDCP State Variable for MBS Multicast reception in RRC INACTIVE | Nokia Corporation |
| R2-2400617 | Misc CR to 38.321 for NR MBS enh | ZTE, Sanechips, CBN |
| R2-2401058 | MAC Reset when switching to RRC_CONNECTED | Sharp |
| R2-2401126 | Discussion on PTM retransmission reception with HARQ feedback disabled | ASUSTeK |
| R2-2401260 | Remaining UP issues for multicast reception in RRC_INACTIVE | Huawei, HiSilicon |
| R2-2401363 | MAC Reset in State Transition from RRC_INACTIVE to RRC_CONNECTED | Samsung |
| R2-2401656 | Summary of [AT125][605][eMBS] Initial PDCP variable (Huawei) | Huawei, HiSilicon |
| R2-2401660 | Summary of [AT125][605][eMBS] Initial PDCP variable (Huawei) | Huawei, HiSilicon |
| 7.11.3 | Shared processing corrections | |
| R2-2400375 | Correction for Shared Processing | Samsung |
| R2-2401261 | Discussion on shared processing for MBS broadcast and unicast reception | Huawei, HiSilicon |
| 7.11.4 | UE capabilities | |
| R2-2400126 | Remaining Issues on UE Capabilities for eMBS | vivo |
| R2-2400244 | Discussion on UE capability remaining issues for eMBS | MediaTek |
| R2-2400267 | Discussion on UE Capability for eMBS | CATT, CBN, China Broadnet |
| R2-2400300 | Discussion on eMBS UE capabilities | Spreadtrum Communications |
| R2-2400316 | Consideration on the open issue for eMBS capabilities | Beijing Xiaomi Software Tech |
| R2-2401087 | UE capability for reception quality based RRC resume | LG Electronics Inc. |
| R2-2401355 | UE capability of MBS quality threshold | Ericsson, Qualcomm Incorporated, AT&T, FirstNet |
| R2-2401356 | MBS capabilities | Ericsson |
| R2-2401653 | Correction on eMBS Capabilities | vivo |
| R2-2401654 | Correction on eMBS Capabilities | vivo, Ericsson |
| R2-2401661 | Reply LS on UE Capability of Multicast Reception in RRC_INACTIVE | RAN2 |
| R2-2401921 | Report of [AT125][603][eMBS] MBS UE capabilities CRs | vivo |
| 7.12.1 | Organizational Stage-2 and high-level open issues | |
| R2-2400035 | Reply LS on UE RACH-less handover for mobile IAB (R3-238048; contact: Qualcomm) | RAN3 |
| R2-2400136 | Reply LS on UE RACH-less handover for mobile IAB | Huawei, HiSilicon |
| R2-2400422 | Discussion on CHO and the reply LS on RACH-less HO in mIAB | ZTE, Sanechips |
| R2-2401012 | Open issue list for mobile IAB UE capabilities | Nokia, Nokia Shanghai Bell |
| R2-2401773 | Updated CE RIL resolutions post R2#125 | Huawei, HiSilicon |
| R2-2401937 | Reply LS on UE RACH-less handover for mobile IAB | RAN2 |
| 7.12.2 | Stage-3 | |
| R2-2400137 | The inheritance of IAB operations to mobile IAB in 38.300 with [H750] [H751] as exclusion | Huawei, HiSilicon |
| R2-2400865 | Mobile IAB-MT gNB-ID acquisition and measurement configuration | Nokia, Nokia Shanghai Bell |
| R2-2401372 | Introduction of Mobile TRP location info | Ericsson |
| R2-2401373 | RILs conclusions for MobileIAB | Ericsson |
| R2-2401694 | RILs conclusions for MobileIAB | Ericsson |
| R2-2401938 | Introduction of Mobile TRP location info | Ericsson |
| 7.12.2.2 | Control plane corrections | |
| R2-2400138 | Remove “best cell” for mobile IAB prioritization in TS 38.304 | Huawei, HiSilicon |
| R2-2400423 | On frequency prioritization for UEs in mobile IAB | ZTE, Sanechips |
| R2-2400424 | Discussion on UE capabilities for mobile IAB-MT | ZTE, Sanechips |
| R2-2400434 | Discussion on RILs for mobile IAB | Qualcomm Inc. |
| R2-2400435 | Remaining issues for UE capabilities for mobile IAB | Qualcomm Inc. |
| R2-2400684 | On mIAB capabilities | Samsung |
| R2-2400717 | Mobile IAB-MT barring | Samsung |
| R2-2400864 | UE capabilities for mobile IAB | Nokia, Nokia Shanghai Bell |
| R2-2400866 | Cell barring for mobile IAB-MT | Nokia, Nokia Shanghai Bell |
| R2-2400921 | RRC open issues on mobile IAB | Apple |
| R2-2400922 | UE capability open issues on mobile IAB | Apple |
| R2-2401237 | [E070] Barring of mobile IAB-MT | LG Electronics Inc. |
| R2-2401371 | Miscellaneous corrections on Mobile IAB | Ericsson |
| R2-2401374 | Discussion on RILs conclusion MobileIAB | Ericsson |
| R2-2401576 | Miscellaneous corrections on Mobile IAB | Ericsson |
| R2-2401811 | CR to 38.306 on UE capabilities for mobile IAB-MT | Qualcomm Inc. |
| R2-2401951 | Summary of offline discussion [AT125][508][mIAB] 306 clarification (QC) | Qualcomm Inc. |
| R2-2401952 | CR to 38.306 on UE capabilities for mobile IAB-MT | Qualcomm Inc. |
| 7.12.2.3 | User plane corrections | |
| R2-2400621 | Handling of DRX and measurement gaps during RACH-less handover | Samsung |
| 7.13.1 | Organizational | |
| R2-2400037 | Reply to LS on AI/ML Core Network enhancements (R3-237745; contact: ZTE) | RAN3 |
| R2-2400091 | Reply LS on MDT for NPN (S5-237504; contact: Ericsson) | SA5 |
| R2-2400219 | Reply LS on improved KPIs involving end-to-end data volume transfer time analytics (S5-241086; contact: Intel, Verizon, CMCC) | SA5 |
| R2-2400658 | WI RIL list for 36.331 for R18 SONMDT | Huawei, HiSilicon |
| R2-2400659 | Corrections to TS 36.331 for R18 SONMDT | Huawei, HiSilicon |
| R2-2400763 | Introduction of Rel-18 MDT enhancements | Nokia, Nokia Shanghai Bell (Rapporteur), ZTE, SaneChips, CMCC |
| R2-2401445 | SONMDT RILs Summary | Ericsson |
| R2-2401505 | Corrections to 38331 for Rel-18 SONMDT | Ericsson |
| R2-2401674 | Introduction of Rel-18 MDT enhancements | Nokia, Nokia Shanghai Bell (Rapporteur), ZTE, SaneChips, CMCC |
| R2-2401681 | Corrections to TS 36.331 for R18 SONMDT | Huawei, HiSilicon |
| R2-2401682 | Corrections to 38331 for Rel-18 SONMDT | Ericsson |
| R2-2401778 | RIL status for 36.331 for R18 SONMDT after RAN2#125 | Huawei, HiSilicon |
| R2-2401779 | RIL list for SONMDT | Ericsson |
| 7.13.2 | Papers related to RILs | |
| R2-2400158 | [V314] logged MDT configuration for SNPN | vivo |
| R2-2400372 | [S515] Correction on release of MHI | Samsung |
| R2-2400374 | [S518] intendedSIBs doesn’t consider R17 and R18 SIBs | Samsung |
| R2-2400376 | Discussion on RIL [S517][S520] | Samsung |
| R2-2400377 | [S513]RSSI measurements for same NR-ARFCN and different SCS | Samsung |
| R2-2400530 | [Z511/514/520]Consideration on NPN remaining issues | ZTE Corporation, Sanechips |
| R2-2400531 | [Z512]Inclusion of PCI and frequency for inter-RAT SHR | ZTE Corporation, Sanechips |
| R2-2400533 | [C307] On includingT316 for failed Fast MCG recovery | ZTE Corporation, Sanechips |
| R2-2400552 | [F001][F018][F019][F020][F021][F022][F023] Correction on SPR | Fujitsu, Lenovo, CATT |
| R2-2400553 | [F002][F024]Correction on SPR | Fujitsu |
| R2-2400660 | Discussion on UE behaviour on releasing sn-InitiatedPSCellChange [H767] | Huawei, HiSilicon |
| R2-2400661 | Discussion on UE behaviour for non SNPN access mode and SNPN access mode [H771] | Huawei, HiSilicon |
| R2-2400662 | Discussion on UE behaviour on releasing the SPR configuration [H779] | Huawei, HiSilicon |
| R2-2400691 | [S516]Issues with Sn-InitiatedPSCellChange handling | Samsung |
| R2-2400761 | RIL N022 - Clarification on location information included in SPR | Nokia, Nokia Shanghai Bell |
| R2-2400779 | Addressing fast MCG recovery related RIL [E011] | Ericsson |
| R2-2400780 | Addressing Inter-RAT SHR and SPR related RILs [E012] [E017] [E142] | Ericsson |
| R2-2400781 | Draft CR on maximum number of NPN identities in MDT configuration [E022] | Ericsson |
| R2-2400912 | [J040][J041][J042]Issues for fast MCG recovery MRO | SHARP Corporation |
| R2-2400914 | [J043][J044]SPR cause setting in a SPR | SHARP Corporation |
| R2-2401091 | [C304]Discussion on the impact brought by SCG activation/deactivation for SPR | CATT |
| R2-2401092 | [C307]Discussion on Fast MCG Recovery MRO Enhancement | CATT |
| R2-2401093 | [C308]Correction on SNPN checking | CATT |
| R2-2401094 | [C311]Correction on CPAC failure | CATT |
| R2-2401095 | [C312] Correction on SPR trigger condition evaluation | CATT,Fujitsu |
| R2-2401096 | [C315]Add the limitation on logged MDT area configuration involving PNI-NPN and SNPN | CATT |
| R2-2401226 | Correction on Area Configuration for NPN in logged Measurement Configuration | Qualcomm Incorporated |
| R2-2401490 | [C303]Correction on including the NR RACH report into the UEInformationResponse message in LTE spec | CATT |
| R2-2401491 | [C304]Discussion on when to retrieve the NR RACH information in LTE spec | CATT |
| R2-2401492 | [C305]Correction on RACH-Report in LTE spec | CATT |
| R2-2401672 | Report of TPs for agreements for TS 36.331 | Huawei, HiSilicon |
| 7.13.3 | Other | |
| R2-2400317 | Consideration on the support of equivalent SNPN in SON/MDT report | Beijing Xiaomi Software Tech |
| R2-2400318 | Consideration on the leftover issues for the RACH optimization | Beijing Xiaomi Software Tech |
| R2-2400532 | Consideration on SPR remaining issues | ZTE Corporation, Sanechips |
| R2-2400663 | Discussion on stage-2 corrections for R18 SONMDT | Huawei, HiSilicon |
| R2-2400664 | Discussion on stage-3 issues for R18 SONMDT | Huawei, HiSilicon |
| R2-2400760 | Adding SPR-Config to CG-Config (Reply LS to R2-2311725/ R3-235868) | Nokia, Nokia Shanghai Bell |
| R2-2400762 | Scenarios for fast MCG recovery | Nokia, Nokia Shanghai Bell |
| R2-2400777 | Discussion on SPR Enhancements | Ericsson |
| R2-2400778 | SON Support for NPN | Ericsson |
| R2-2401090 | Consideration on the open issues for SONMDT | CATT |
| R2-2401141 | Support of RACH optimization in RRC Spec | CMCC, ZTE, Sanechips, Huawei, HiSilicon, Ericsson |
| R2-2401229 | Clarification on RAInformationCommon Reporting in SPR | Qualcomm Incorporated |
| R2-2401516 | Discussion on stage-3 issues for R18 SONMDT | Huawei, HiSilicon |
| R2-2401675 | [DRAFT] Reply LS on SPR | Nokia |
| R2-2401685 | Reply LS on SPR | RAN2 |
| 7.14.1 | Organizational | |
| R2-2400042 | LS on QMC support in RRC_IDLE and RRC_INACTIVE (R3-237997; contact: ZTE) | RAN3 |
| R2-2400043 | Support for MCE ID (R3-238003; contact: Ericsson) | RAN3 |
| R2-2400070 | Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE (S2-2313777; contact: ZTE) | SA2 |
| R2-2400087 | LS Reply on area scope for QoE measurements (S4-231905; contact: Huawei) | SA4 |
| R2-2400090 | Reply LS on area scope for QoE measurements (S5-238098; contact: Ericsson) | SA5 |
| R2-2400201 | Stage-2 CR for Rel-18 NR QoE enhancement | China Unicom, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2400214 | Reply LS on Support for MCE ID (S5-240021; contact: Ericsson) | SA5 |
| R2-2400782 | Correction of Enhancement on NR QoE management and optimizations for diverse services | Ericsson |
| R2-2400783 | RIL issues for QoE | Ericsson |
| R2-2400787 | Proposal for Reply LS on area scope for QoE measurements | Ericsson |
| R2-2401131 | CR for RAN visible QoE measurements and reporting in NR-DC | Nokia, Nokia Shanghai Bell, China Unicom |
| R2-2401658 | Reply LS on area scope handling for QoE measurements | RAN2 |
| R2-2401659 | Stage-2 CR for Rel-18 NR QoE enhancement | China Unicom, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2401665 | RIL issues for QoE after RAN2#125 | Ericsson |
| R2-2401666 | Correction of Enhancement on NR QoE management and optimizations for diverse services | Ericsson, Samsung |
| R2-2401696 | LS on area scope handling for QoE measurement collection (C1-241717; contact: Ericsson) | CT1 |
| 7.14.2 | QoE measurements in RRC_IDLE INACTIVE | |
| R2-2400539 | Remaining issues on QoE for RRC IDLE and INACTIVE | ZTE Corporation, Sanechips |
| R2-2400784 | Open issues for QoE measurements | Ericsson |
| R2-2400785 | Further RIL issues related to QoE measurements | Ericsson |
| R2-2401079 | Discussion on E006, S682, S683, and S684 | Samsung |
| R2-2401103 | Discussion on remaining issues for QoE measurements in RRC IDLE and INACTIVE state | CATT |
| R2-2401105 | [C322]Discussion on how to handle the QoE report generated after UE entering RRC_CONNECTED state | CATT |
| R2-2401106 | [C325]Discussion on how to configure UE to report QoE session status | CATT |
| R2-2401132 | Discussion on RRC open issues RIL [N013] and [E098] | Nokia, Nokia Shanghai Bell |
| R2-2401159 | Remaining issues on QoE for IDLE and Inactive state | Qualcomm Incorporated |
| R2-2401423 | QoE report discarding [H706] | Huawei, HiSilicon |
| R2-2401425 | The need of configForRRC-IdleInactive [H716] | Huawei, HiSilicon |
| R2-2401426 | Discussion on open issues for QoE measurements in RRC_IDLE and INACTIVE | Huawei, HiSilicon |
| 7.14.3 | Support of QoE measurements for NR-DC | |
| R2-2400540 | Remaining issues on QoE for NR-DC | ZTE Corporation, Sanechips |
| R2-2401080 | Discussion on S681 and a remaining issue in NR-DC QoE | Samsung |
| R2-2401424 | Spare values for reportingSRB [H720] | Huawei, HiSilicon |
| 7.14.4 | UE capabilities | |
| R2-2400541 | Discussion on inter-RAT QoE continuity and UE capabilities | ZTE Corporation, Sanechips |
| R2-2401081 | Discussion on memory requirement for QoE measurement | Samsung |
| R2-2401104 | Discussion on the remaining issues for UE capabilities for QoE | CATT |
| R2-2401152 | Discussion on remaining open issue for QoE UE capabilities | CMCC |
| R2-2401161 | RedCap UE QoE capabilities | Qualcomm Incorporated |
| R2-2401427 | Discussions on open issues for UE capabilities | Huawei, HiSilicon |
| R2-2401657 | Correction of Rel-18 QoE (e)RedCap UE memory requirement | CMCC |
| 7.14.5 | Other | |
| R2-2400786 | Other open issues for QoE | Ericsson |
| R2-2401133 | On FFS for LTE QoE configurations release for inter-RAT HO from LTE to NR [E099] | Nokia, Nokia Shanghai Bell |
| R2-2401160 | QoE configuration handling during inter-RAT mobility | Qualcomm Incorporated |
| R2-2401428 | Other QoE open issues | Huawei, HiSilicon |
| R2-2401493 | How to handle the collision of handling of QoE configuration during IRATHO in stage 2 spec | CATT |
| 7.15.1 | Organizational | |
| R2-2400082 | Reply LS on QoS to Carrier Mapping for SL CA (S2-2401579; contact: Qualcomm) | SA2 |
| R2-2400083 | Reply LS on Tx profile for SL CA (S2-2401581; contact: LGE) | SA2 |
| R2-2400230 | RRC Open Issue list for R18 SL-Evo | OPPO |
| R2-2400909 | MAC open issue list for R18 SL-Evo | LG Electronics France |
| R2-2401704 | Reply to LS on Sidelink CSI Reporting MAC-CE for SL-CA (R1-2401727; contact: LGE) | RAN1 |
| R2-2401709 | LS on new higher layer parameter for intra-cell guard band (R1-2401756; contact: OPPO) | RAN1 |
| 7.15.2 | RRC corrections | |
| R2-2400151 | Discussion on remaining issues on control plane for SL evo | ZTE Corporation, Sanechips |
| R2-2400207 | Discussion and TP on QoS flow to DRB mapping based on SA2 LS | vivo |
| R2-2400231 | Correction on Release-18 SL Evolution | OPPO |
| R2-2400241 | Discussion on S2-2401579 | OPPO |
| R2-2400242 | Discussion on [O312, X011] | OPPO, Xiaomi |
| R2-2400243 | Discussion on [O301, X010] | OPPO, Xiaomi |
| R2-2400247 | RIL list for R18 SL | OPPO |
| R2-2400257 | [C613] [C614] Essential corrections and left issues in RRC for Rel-18 NR SL evolution | CATT |
| R2-2400295 | [X005] Correction on additional RLC bearer release for SL | Xiaomi |
| R2-2400296 | [X006] Correction on additonal RLC bearer addition and modification for RRC connected UE | Xiaomi |
| R2-2400297 | [X015][O306]Correction on the value of carrier ID | Xiaomi, OPPO |
| R2-2400371 | [Y003] SL-TxProfiles and their extensions | TOYOTA Info Technology Center |
| R2-2400398 | [X020] Correction on SL carrier addition/release/modification triggered SUI | Xiaomi |
| R2-2400510 | Discussion issues for 38.331 | Ericsson |
| R2-2400511 | Discussion and TP on RIL E042 | Ericsson |
| R2-2400512 | Discussion and TP on RIL E089 | Ericsson |
| R2-2400513 | Discussion and TP on RIL E040 E041 E088 and O309 | Ericsson, OPPO |
| R2-2400522 | RRC corrections for SL evolution | Huawei, HiSilicon |
| R2-2400525 | [H623] Discussion on carrier failure caused by RLC AM failure | Huawei, HiSilicon |
| R2-2400526 | [H624] Discussion on the distinction between RLF failure and carrier failure caused by DTX | Huawei, HiSilicon |
| R2-2400527 | [H643] Discussion on carrier set when PDCP duplication is not used | Huawei, HiSilicon |
| R2-2400528 | [H645] Discussion on PDCP duplication configuration via SIB or preconfiguration | Huawei, HiSilicon |
| R2-2400529 | [H646] Discussion on PDCP duplication for default SLRB via SIB or preconfiguration | Huawei, HiSilicon |
| R2-2400947 | Discussion on SA2 Reply LS on QoS flow mapping issue | Apple |
| R2-2401077 | Addressing Open Issue on QoS Flow to Carrier Mapping | InterDigital |
| R2-2401119 | Discussion on QoS flow mapped carriers for SL CA | Qualcomm India Pvt Ltd |
| R2-2401188 | Input to the RILs for SL evolution | Nokia, Nokia Shanghai Bell |
| R2-2401781 | Correction on Release-18 SL Evolution | OPPO |
| R2-2401782 | RIL list for R18 SL | OPPO |
| R2-2401794 | Summary of [AT125][106][V2X/SL]: SL-U carrier + SL CA carriers (including the proposal) | CATT |
| R2-2402035 | Correction on R18 SL | OPPO |
| 7.15.3 | MAC corrections | |
| R2-2400152 | Discussion on remaining issues on user plane for SL evo | ZTE Corporation, Sanechips |
| R2-2400177 | Discussion on MAC open issue of SL enhancement | China Telecom |
| R2-2400208 | Discussion on LCP enhancement in case of discovery pool configuration | vivo |
| R2-2400220 | Remaining MAC Open Issue for NR SL with multiple carriers | Lenovo |
| R2-2400232 | Left issues on MAC | OPPO |
| R2-2400233 | Discussion on Use-Case for SL-U and SL-CA | OPPO |
| R2-2400258 | Essential corrections and left open issues in MAC for Rel-18 NR SL evolution | CATT |
| R2-2400260 | Text Proposal for MAC Rel-18 corrections on Sidelink resource allocation and Sidelink LBT failure | TOYOTA Info Technology Center, Lenovo |
| R2-2400270 | Corrections on SL-U for MAC layers | SHARP Corporation |
| R2-2400294 | Correction on TS 38.321 for SL | Xiaomi |
| R2-2400301 | Issues on TX carrier (re-)selection | Spreadtrum Communications |
| R2-2400515 | Discussion on MAC issues | Ericsson |
| R2-2400523 | MAC corrections for SL evolution | Huawei, HiSilicon |
| R2-2400773 | Selection of logical channels for SL-U | Nokia, Nokia Shanghai Bell |
| R2-2400913 | Discussion on MAC open issues for R18 SL-Evo | LG Electronics France |
| R2-2400923 | Open issues on Rel-18 SL evolution | Apple |
| R2-2400946 | Discussion on IUC MAC CEs for SL-U | Apple |
| R2-2400962 | MAC corrections on Rel-18 NR sidelink evolution | LG Electronics France |
| R2-2400979 | Discussion on enhanced LCP | LG Electronics France |
| R2-2401078 | Addressing Open Issues on MAC Layer | InterDigital |
| R2-2401121 | Draft LS on co-channel co-existence | LG Electronics |
| R2-2401125 | Corrections for MAC | Qualcomm Incorporated |
| R2-2401488 | Miscellaneous correction for SL enhancement for TS38.321 | NEC |
| R2-2401783 | MAC corrections on Rel-18 NR sidelink evolution | LG Electronics France |
| R2-2401784 | Summary of Offline -103, IUC MAC CE in Rel-18 SL Evo | Apple (Rapporteur) |
| R2-2401785 | Text Proposal for Offline-103 on IUC MAC CEs in Rel-18 | Apple(rapporteur) |
| R2-2401786 | Summary of [AT125][104][V2X/SL] Others offline discussion (LG) | LG Electronics Inc. |
| R2-2401795 | Text Proposal for Offline-103 on IUC MAC CEs in Rel-18 | Apple |
| R2-2401796 | LS on IUC or DRX in co-channel co-existence | RAN2 |
| R2-2402036 | MAC corrections on Rel-18 NR sidelink evolution | LG Electronics France |
| R2-2402041 | MAC corrections on Rel-18 NR sidelink evolution | LG |
| 7.15.4 | Others | |
| R2-2400153 | Discussion on Tx profile for SL CA | ZTE Corporation, Sanechips |
| R2-2400256 | Essential Corrections on NR SL evolution in Stage 2 Spec | CATT |
| R2-2400292 | Correction on TS 38.300 for SL | Xiaomi |
| R2-2400293 | Correction on TS 38.304 for SL | Xiaomi |
| R2-2400514 | Discussion issues for 38.300 | Ericsson |
| R2-2400524 | Misc corrections for SL evolution | Huawei, HiSilicon |
| R2-2400769 | Introduction of sidelink coexistense to 38.300 | Nokia, Nokia Shanghai Bell |
| R2-2401076 | Rapporteur Stage 2 Corrections for NR Sidelink Evolution | InterDigital |
| R2-2401489 | Miscellaneous correction for SL enhancement for TS38.300 | NEC |
| R2-2401788 | Miscellaneous Stage 2 Corrections for NR Sidelink Evolution | InterDigital |
| 7.17.1 | Organizational | |
| R2-2401065 | Correction on NR MUSIM enhancements | vivo |
| R2-2401066 | [POST124][MUSIM][38331] Open Issue list(vivo) | vivo |
| R2-2401067 | RILs_conclusion_MUSIM | vivo |
| R2-2401068 | Discussion on RILs conclusion_MUSIM | vivo |
| R2-2401251 | Corrections to TS 38.300 for R18 MUSIM | China Telecom, Huawei, HiSilicon |
| R2-2401551 | Corrections to TS 38.300 for R18 MUSIM | China Telecom, Huawei, HiSilicon |
| R2-2401553 | Correction on NR MUSIM enhancements | vivo |
| R2-2401554 | RILs_conclusion_MUSIM | vivo |
| 7.17.2 | RRC | |
| R2-2400112 | Discussion on remaining open issues for MUSIM | CATT |
| R2-2400114 | [O100] Discussion on Timer T346n | OPPO |
| R2-2400115 | [O101] Discussion on Reporting Maximum Number of CC | OPPO |
| R2-2400116 | [O102] Discussion on Need for Gap Requirements for MUSIM Purpose | OPPO |
| R2-2400545 | Discussion on open issue for early indication | Huawei, HiSilicon |
| R2-2400546 | [H035] Discussion on Early Indication for Resume Request with no configuration | Huawei, HiSilicon |
| R2-2400593 | Discussion on open issues for temporary capability restriction | Huawei, HiSilicon |
| R2-2400594 | Discussion on open issues in NR-DC and Handover | Huawei, HiSilicon |
| R2-2400605 | Remaining issue of MUSIM temporary capability restriction | NEC |
| R2-2400618 | [RIL-S851] Capability restriction and RRC Reestablishment | Samsung |
| R2-2400619 | [RIL-S852] Remaining issues for Musim-NeedForGaps | Samsung |
| R2-2400776 | [S857] Start / Restart Wait Timer for UAI during HO and CHO | Samsung |
| R2-2401013 | [RIL-S853] No capability restriction in first UAI after early indication | Samsung, Huawei, HiSilicon |
| R2-2401015 | Considerations on Open issues for R18 MUSIM | LG Electronics |
| R2-2401017 | Remaining Issues on the Temporary Capability Reporting Procedure | ZTE Corporation, Sanechips |
| R2-2401018 | Remaining Issues on the Temporary Capability Reporting | ZTE Corporation, Sanechips |
| R2-2401019 | Remaining Issues on the MUSIM Gap | ZTE Corporation, Sanechips |
| R2-2401036 | Remaining consideration on MUSIM early indication | DENSO CORPORATION |
| R2-2401038 | Further discussion on Rel-17 MUSIM UAI and Rel-18 UAI Interworking | Nokia, Nokia Shanghai Bell |
| R2-2401039 | Temporary capability restriction related open issues | Nokia, Nokia Shanghai Bell |
| R2-2401040 | Additional capability restrictions related to measurement gaps | Nokia, Nokia Shanghai Bell |
| R2-2401069 | Discussion on the remaining issue of MUSIM temporary capability restriction | vivo |
| R2-2401070 | Discussion on the remaining issue of MUSIM early indication | vivo |
| R2-2401071 | [C010][Z102]Discussion on musim-GapProhibitTimer | vivo |
| R2-2401180 | Discussion on Q622 and Q623 | Qualcomm Incorporated |
| R2-2401190 | InterNode communictaion for temporary capability restrictions [S854] [OI5][OI6] | Samsung |
| R2-2401192 | Discussion on temporary capability restriction and handover [OI2] | Samsung |
| R2-2401193 | Discussion on S858, Z101, C007 | Samsung Electronics Czech |
| R2-2401197 | Discussion on compliance check in RRCReconfiguration for MUSIM | Samsung Electronics Czech |
| R2-2401254 | Discussion on remaining open issues for MUSIM | China Telecom |
| R2-2401340 | Open issues on MUSIM Band restrictions | Ericsson |
| R2-2401341 | Discussion on remaining MUSIM open issues | Ericsson |
| R2-2401495 | [RIL-Z102] MUSIM Gap UAI Processing | ZTE Corporation, Sanechips |
| R2-2401552 | On Issue#6 FFS on additional info on how the network set the content of MUSIM band list filter | Huawei, HiSilicon |
| 7.17.3 | Other | |
| R2-2401339 | Modification of UE capability for MUSIM | Ericsson |
| 7.18.1 | Organizational | |
| R2-2400335 | Rapporteur CR to MT-SDT and CG-SDT enhanccement [CG-SDTenh] | Huawei, HiSilicon, Ericsson |
| R2-2400754 | SDT RIL resolutions for ASN.1 review | ZTE Corporation (rapporteur) |
| R2-2400755 | SDT corrections for ASN.1 Review issues | ZTE Corporation, Ericsson (rapporteurs) |
| R2-2401573 | SDT corrections for ASN.1 Review issues [CG-SDT-enh] | ZTE Corporation, Ericsson (rapporteurs) |
| R2-2401780 | SDT RIL resolutions for ASN.1 review | ZTE Corporation (rapporteur) |
| 7.18.2 | Others | |
| R2-2400585 | Small Data Transmissions Control Plane | Ericsson |
| R2-2401429 | Missing indication from RRC to MAC on SDT procedure type [H700] | Huawei, HiSilicon |
| 7.19.1 | Organizational | |
| R2-2400009 | Reply LS on INACTIVE eDRX above 10.24sec and SDT (C4-235535; contact: Ericsson) | CT4 |
| R2-2400024 | LS on eRedCap agreements on early indication in MsgA PRACH and on peak rate related capability parameters (R1-2312618; contact: Ericsson) | RAN1 |
| R2-2400075 | Reply LS on INACTIVE eDRX above 10.24sec and SDT (S2-2313911; contact: Ericsson) | SA2 |
| R2-2400080 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 (S2-2401530; contact: Huawei) | SA2 |
| R2-2400456 | Miscellaneous corrections on TS 38.321 for eRedCap | vivo (Rapporteur) |
| R2-2400595 | Draft_Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | Huawei, HiSilicon |
| R2-2400875 | Miscellaneous corrections for eRedCap | Ericsson |
| R2-2400877 | RIL list for eRedCap | Ericsson |
| R2-2401008 | Correction on eRedCap | OPPO, Huawei |
| R2-2401053 | Discussion on SA2 LS regarding the RedCap and eRedCap capabilities | Qualcomm Incorporated |
| R2-2401697 | LS on Rel-18 RedCap enhancements work (C1-241809; contact: Huawei) | CT1 |
| R2-2401705 | LS on separate CFR introduced in Rel-18 TEI of MBS for RedCap UE applied for eRedCap UE (R1-2401732; contact: ZTE) | RAN1 |
| R2-2401768 | Draft_Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | Huawei, HiSilicon |
| R2-2401881 | Miscellaneous corrections for eRedCap | Ericsson |
| R2-2401882 | Correction of MDT logged measurement memory requirement for eRedCap | Intel Corporation |
| R2-2401883 | Miscellaneous corrections on TS 38.321 for eRedCap | vivo (Rapporteur) |
| R2-2401888 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | RAN2 |
| R2-2401889 | Miscellaneous corrections for eRedCap | Ericsson |
| 7.19.2 | Papers related to RILs | |
| R2-2400323 | [X110] Clarification on eRedcap MsgA PUSCH and proposed TP to RRC | Xiaomi Communications |
| R2-2400457 | [V171 V172] Clarification on eRedCapIgnoreCapabilityFiltering | vivo, Guangdong Genius |
| R2-2400458 | [V173 V174 V175] Clarification on ran-ExtendedPagingCycle-r18 | vivo, Guangdong Genius |
| R2-2400459 | [V176] Discussion on the fallback configuration for eDRX in RRC inactive | vivo, Guangdong Genius |
| R2-2400460 | [V177 V178] Discussion on reduced requirements for logged MDT and RA report for eRedCap | vivo, Guangdong Genius |
| R2-2400461 | [V179] Discussion on the missing case for only RedCap and only eRedCap | vivo, Guangdong Genius |
| R2-2400597 | [H738] [V170] Discussion on eRedCap specific initial DL or UL BWP | Huawei, HiSilicon, vivo |
| R2-2400598 | [H739] Discussion on eRedCap capability filtering | Huawei, HiSilicon |
| R2-2400599 | [H742] [X110] Discussion on the restriction of using 2-step RACH for eRedCap UE | Huawei, HiSilicon |
| R2-2401478 | [V171 V172] Clarification on eRedCapIgnoreCapabilityFiltering | vivo, Guangdong Genius |
| R2-2401479 | [V173 V174 V175] Clarification on ran-ExtendedPagingCycle-r18 | vivo, Guangdong Genius |
| R2-2401480 | [V176] Discussion on the fallback configuration for eDRX in RRC inactive | vivo, Guangdong Genius |
| R2-2401481 | [V177 V178] Discussion on reduced requirements for logged MDT and RA report for eRedCap | vivo, Guangdong Genius |
| R2-2401482 | [V179] Discussion on the missing case for only RedCap and only eRedCap | vivo, Guangdong Genius |
| R2-2401721 | List of eRedCap WI RILs with no Tdoc | Ericsson |
| 7.19.3 | Other | |
| R2-2400324 | Remaining issues on the use of 2-step RA resources for eRedCap UEs and proposed TP to RRC | Xiaomi Communications |
| R2-2400462 | Discussion on remaining issues for eRedCap | vivo, Guangdong Genius |
| R2-2400596 | Discussion on two step RA issue and peak data rate LS for eRedCap | Huawei, HiSilicon |
| R2-2400827 | 1 Rx and 2 Rx eRedCap UE barring | Nokia, Nokia Shanghai Bell |
| R2-2400878 | Discussion on fallback from 2-step to 4-step RA for eRedCap UEs | Ericsson |
| R2-2400986 | Remaining issues on eRedCap | LG Electronics Inc. |
| R2-2401052 | Discussion on SON/MDT reports for eRedCap | Qualcomm Incorporated |
| R2-2401122 | Discussion on eRedCap remaining open issue | NEC Corporation |
| R2-2401240 | Remaining issues of RA resources selection for eRedCap (MAC) | ZTE Corporation, Sanechips |
| R2-2401395 | Remaining issues on eRedcap | Sequans Communications |
| R2-2401769 | [DRAFT] LS on 2-step for eRedCap | Ericsson |
| R2-2401770 | Correction on (e)Redcap 1 Rx and 2 Rx barring | Nokia, Nokia Shanghai Bell |
| R2-2401844 | Remaining issues on the use of 2-step RA resources for eRedCap UEs and proposed TP to RRC | Xiaomi Communications |
| R2-2401890 | LS on 2-step for eRedCap | RAN2 |
| 7.20.1 | Organizational | |
| R2-2400013 | LS to RAN2 on TDCP for Rel-18 MIMO (R1-2312382; contact: Samsung) | RAN1 |
| R2-2400600 | RIL List v212 | Ericsson |
| R2-2400601 | Correction to MIMO Evolution | Ericsson |
| R2-2401328 | Open issue list for MIMO evolution | NTT DOCOMO, INC. |
| R2-2401555 | Corrections on Rel-18 MIMOevo for TS 38.321 | Samsung |
| R2-2401556 | Correction to MIMO Evolution | Ericsson |
| R2-2401557 | RIL List v212 | Ericsson |
| R2-2402024 | Correction to MIMO Evolution | Ericsson |
| R2-2402048 | Corrections on Rel-18 MIMOevo for TS 38.321 | Samsung |
| 7.20.2 | MAC | |
| R2-2400163 | Discussion on the UE behaviors for the MTTD issue for 2 PTAGs | Xiaomi |
| R2-2400174 | Discussion on open issue of multiple TA operation | OPPO |
| R2-2400175 | Discussion on PHR report for mTRP operation | OPPO |
| R2-2400176 | Discussion on UL grant handling for STxMP | OPPO |
| R2-2400245 | Discussion on the Listed MAC Open Issues | CATT |
| R2-2400246 | MAC Corrections on the Unified TCI Extension to mTRP | CATT, Ericsson |
| R2-2400470 | Discussion on left issues of two TAs for multiple TRPs | SHARP Corporation |
| R2-2400581 | MAC issues for STxMP | Ericsson |
| R2-2400811 | Remaining issues on MIMO | Samsung |
| R2-2400820 | Overlapping UL grants handling for STxMP | Huawei, HiSilicon |
| R2-2400899 | Remaining issues on two TAG | LG Electronics Inc. |
| R2-2400900 | Discussion on STxMP PHR | LG Electronics Inc. |
| R2-2400901 | Remaining issue on UL grant handling for STxMP | LG Electronics Inc. |
| R2-2401042 | Remaining issues on STxMP | Qualcomm Incorporated |
| R2-2401046 | Cosideration On Supporting STxMP in RAN2 | ZTE Corporation, Sanechips |
| R2-2401048 | Considerations On Remaining Issues for 2TA | ZTE Corporation, Sanechips |
| R2-2401200 | Random Access problem for SpCell with two TAGs | Langbo |
| R2-2401205 | Support of STxMP PHR for Single-DCI based Multiple TRP | Samsung, Ericsson |
| R2-2401305 | MAC issue with TAT expiry and 2TA | Nokia, Nokia Shanghai Bell |
| R2-2401306 | CG-SDT TAT and 2TA | Nokia, Nokia Shanghai Bell |
| R2-2401307 | TAT handling when MTTD is exceeded for PTAGs | Nokia, Nokia Shanghai Bell |
| R2-2401330 | Discussion on open issues on MIMO evolution | NTT DOCOMO, INC. |
| 7.20.3 | RRC | |
| R2-2400591 | H045(on CodebookConfig-r18) | Ericsson |
| R2-2400818 | Open issues on 2TA for mTRP | Huawei, HiSilicon |
| R2-2400819 | [H070] Codebook configuration for CJT mTRP | Huawei, HiSilicon |
| R2-2400826 | RRC RIL S872, S882, S893, S894, C506 | Samsung |
| R2-2401047 | Miscellneous on RRC For MIMO evo | ZTE Corporation, Sanechips |
| 7.21.1 | Organizational | |
| R2-2400012 | Reply LS on PHR reporting (R1-2312339; contct: InterDigital) | RAN1 |
| R2-2400046 | LS reply on further clarifications on enhancements to realize increasing UE power high limit for CA and DC (R4-2321998; contact: Huawei) | RAN4 |
| R2-2400060 | LS on UE capabilities for MPR reduction (R4-2321960; contact: Nokia) | RAN4 |
| R2-2400131 | Miscellaneous corrections to CE in RRC | Huawei, HiSilicon |
| R2-2400183 | Stage-2 CR for Further NR coverage enhancements | China Telecom |
| R2-2401438 | Miscellaneous MAC corrections for CE | ZTE Corporation |
| R2-2401536 | CE RIL resolutions | Huawei, HiSilicon |
| R2-2401700 | Reply LS on UE capabilities for MPR reduction (R1-2401627; contact: Nokia) | RAN1 |
| R2-2401771 | Miscellaneous corrections to CE in RRC | Huawei, HiSilicon |
| R2-2401772 | Miscellaneous MAC corrections for CE | ZTE Corporation |
| R2-2401815 | LS on power class capability for NR coverage enhancement (R4-2403659; contact: LGE) | RAN4 |
| 7.21.2 | Control plane corrections | |
| R2-2400133 | Discussion on open issues on control plane for CE | Huawei, HiSilicon |
| R2-2400328 | [H501][H815][H505] Modeling OdSI request with msg1 repetition as RACH feature | Huawei, HiSilicon |
| R2-2400586 | Discussion on Coverage Enhancements Control Plane | Ericsson |
| R2-2400984 | Support of Msg1 repetition for eRedCap UEs | LG Electronics Inc. |
| R2-2401101 | Discussion on the CP remaining issues of CE | CATT |
| R2-2401308 | Capability for DPC reporting | Nokia, Nokia Shanghai Bell |
| R2-2401439 | Remaining CP issues for CE | ZTE Corporation |
| R2-2401500 | Support of Msg1 repetition for eRedCap UEs | LG Electronics Inc. |
| R2-2401774 | Report of [AT125][CE_enh][801] | LG Electronics |
| 7.21.3 | User plane corrections | |
| R2-2400127 | Remaining UP Issues on eCovEnh | vivo |
| R2-2400132 | Discussion on open issues on user plane for CE | Huawei, HiSilicon |
| R2-2400181 | Discussion of PRACH repetition for TN and NTN | China Telecom |
| R2-2400198 | Correction to PHR MAC CE Design for assumed PUSCH reporting | Samsung Electronics Co., Ltd |
| R2-2400262 | CFRA with Msg1 Repetition - RO Mask handling | Samsung Electronics Co., Ltd |
| R2-2400290 | Discussion on on initialization of RRC parameter in RA procedure | Xiaomi |
| R2-2400584 | Discussion on Coverage Enhancements User Plane | Ericsson |
| R2-2400620 | Discussion on the remaining UP issues | NEC Corporation. |
| R2-2400793 | Open Issues in Coverage Enhancements UP | Qualcomm Incorporated |
| R2-2400916 | Clarification on Multiple Entry PHR with Assumed PUSCH | vivo |
| R2-2400985 | Remaining UP issues on Coverage Enhancement | LG Electronics Inc. |
| R2-2401102 | Discussion on the UP remaining issues of CE | CATT |
| R2-2401309 | Miscellaneous on DWS | Nokia, Nokia Shanghai Bell |
| R2-2401440 | Remaining UP issues for CE | ZTE Corporation |
| R2-2401775 | Summary for [AT125][CE_enh][803] Details of ra ssb Occasion Mask Index for CFRA with Msg1 repetition | Samsung |
| 7.23.1 | Organizational | |
| R2-2400580 | Resolution on Open Issues for URLLC TRS | Ericsson |
| R2-2400977 | Correction on UAI for URLLC | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R2-2401869 | Corrections to URLLC and Timing Resiliency | Ericsson (Rapporteur) |
| R2-2401874 | Correction on UAI for URLLC | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R2-2401876 | Resolution on Open Issues for URLLC TRS | Ericsson |
| 7.23.2 | General | |
| R2-2400978 | AS/NAS interaction for timing synchronization status change | Nokia, Nokia Shanghai Bell |
| R2-2401337 | Remaining issues of gNB Identity and EventID handling | ZTE Corporation, Sanechips |
| R2-2401398 | [V509][V510] Remaining Issues on gNB ID Derivation | vivo |
| 7.24.1 | TEI proposals by Other Groups | |
| R2-2400066 | LS reply for Reply LS on Mitigation of Downgrade attacks (S3-234991; contact: Nokia) | SA3 |
| R2-2400094 | Introduction of QCL-TypeD priorities for overlapping CORESETs in M-DCI/M-TRP operation [QCL-TypeD CORESET priority for M-TRP] | CATT |
| R2-2400095 | Introduction of MAC CE based PL RS updates for Type-1 CG-PUSCH [PL RS Type 1 CG] | CATT |
| R2-2400096 | On RRC impact for RAN1 TEI18 feature Multiple PUSCHs scheduling by single DCI for non-consecutive slots in FR1 | CATT |
| R2-2400159 | 38.331 CR for MAC CE based pathloss RS updates for Type 1 CG-PUSCH | Xiaomi |
| R2-2400160 | 38.306 CR for MAC CE based pathloss RS updates for Type 1 CG-PUSCH | Xiaomi |
| R2-2400199 | Handling RRCRelease with resume indication for SDT | Samsung Electronics Co., Ltd |
| R2-2400215 | Reply LS on Multiple Trace/MDT configurations (S5-240798; contact: Ericsson) | SA5 |
| R2-2400753 | Open issues of SDT release enhancement | ZTE Corporation, Sanechips |
| R2-2401274 | Introduction of MAC CE based PL-RS update for Type 1 CG-PUSCH | Huawei, HiSilicon |
| R2-2401275 | Introduction of two QCL-TypeD properties identification and monitoring | Huawei, HiSilicon |
| R2-2401276 | Introduction of RRC parameters for HARQ multiplexing | Huawei, HiSilicon |
| R2-2401304 | Resume indication in RRCRelease | Nokia, Nokia Shanghai Bell |
| R2-2401320 | Introduction of LCS User Plane | Ericsson |
| R2-2401332 | [RIL I054] UE behaviour when providing both resumeIndication-r18 and sdt-Config-r17 [SDT_ReleaseEnh] | Intel Corporation |
| R2-2401412 | Discussion on issues about resumeIndication in RRCRelease | Huawei, HiSilicon, Qualcomm, CATT, Lenovo |
| R2-2401537 | Introduction of QCL-TypeD priorities for overlapping CORESETs in M-DCI/M-TRP operation [QCL-TypeD CORESET priority for M-TRP] | CATT |
| R2-2401538 | Introduction of MAC CE based PL RS updates for Type-1 CG-PUSCH [PL RS Type 1 CG] | CATT |
| R2-2401698 | Reply LS on Mitigation of Downgrade attacks (C1-2418486; contact: Apple) | CT1 |
| R2-2401797 | Reply LS on Trace functionality extension in N3IWF for non-3GPP access scenarios (R3-241066; contact: Ericsson) | RAN3 |
| R2-2401798 | Reply LS on user consent for trace reporting (R3-241115; contact: Ericsson) | RAN3 |
| R2-2401931 | Resume indication in RRCRelease [SDT_ReleaseEnh] | Nokia, Nokia Shanghai Bell |
| R2-2401940 | Introduction of RRC parameters for HARQ multiplexing | Huawei, HiSilicon |
| R2-2401966 | Introduction of Multiple PUSCH scheduling by single DCI for non-consecutive slots in FR1 [M-PUSCH in FR1] | CATT |
| R2-2401977 | Introduction of RRC parameters for HARQ multiplexing [HARQ-ACK MUX on PUSCH] | Huawei, HiSilicon |
| 7.24.2 | TEI proposals by RAN2 | |
| R2-2400006 | LS on the impact of supporting multicast MBS session and Broadcast MBS session for UEs using eDRX (C1-239661; contact: Nokia) | CT1 |
| R2-2400040 | Reply LS to SA2 on RedCap UE MBS Broadcast reception (R3-237959; contact: ZTE) | RAN3 |
| R2-2400078 | Reply LS on RedCap UE MBS Broadcast reception (S2-2401506; contact: Nokia) | SA2 |
| R2-2400268 | Discussion on SA2 LS on RedCap UE MBS Broadcast Reception | CATT |
| R2-2400269 | Correction to 38.300 for redcap CFR of MBS | CATT, CBN, China Broadnet |
| R2-2400615 | Discussion on LS about MBS FSA ID for the RedCap UEs (with draft reply LS) | ZTE, Sanechips |
| R2-2400906 | FSAI for RedCap UE vs non-RedCap UE broadcast reception | Nokia, Nokia Shanghai Bell |
| R2-2400908 | Reply LS on RedCap UE MBS Broadcast reception | Nokia, Nokia Shanghai Bell |
| R2-2400955 | Remaining Issue on Broadcast CFR for Redcap | vivo |
| R2-2401016 | Discussion on SA2 LS on RedCap UE MBS Broadcast Reception | Samsung |
| R2-2401174 | eDRX and MICO | Nokia, Nokia Shanghai Bell |
| R2-2401176 | Supported channel bandwidths in SIB | Nokia, Nokia Shanghai Bell |
| R2-2401266 | Clarification on MBS search spaces configuration for Redcap | Huawei, HiSilicon |
| R2-2401267 | Correction on MBS search spaces configuration for Redcap | Huawei, HiSilicon |
| R2-2401268 | Discussion on the reply to SA2 on RedCap UE MBS Broadcast reception | Huawei, HiSilicon |
| R2-2401354 | MBS multicast with eDRX and MICO mode | Ericsson |
| R2-2401357 | SA2 questions about MBS RedCap CFR | Ericsson |
| R2-2401358 | MBS RedCap CFR in Stage 2 | Ericsson |
| R2-2401391 | Enhancing leaving and entering conditions in measurement report [meas_enter_leave] | Ericsson, T-Mobile USA, Turkcell, Rakuten Mobile, BT Plc., NTT Docomo, Deutsche Telekom, MediaTek Inc., Verizon |
| R2-2401662 | Reply LS on RedCap UE MBS Broadcast reception | RAN2 |
| 7.24.2.1 | 2Rx XR | |
| R2-2400144 | Signaling support for 2Rx non-RedCap XR UEs | Qualcomm Incorporated, BT plc, Ericsson, Meta, Nokia, Nokia Shanghai Bell |
| R2-2400238 | Discussion on 2Rx XR device | OPPO |
| R2-2400544 | UE Capability Report and Access Control for 2Rx non-REDCAP XR devices | MediaTek Inc. |
| R2-2400582 | Support of initial access for 2 RX XR devices in Legacy Networks | Vodafone, Verizon, Apple |
| R2-2400667 | On signaling support for 2Rx non-RedCap XR UEs | Futurewei |
| R2-2400747 | 2RX capability for XR | ZTE Corporation, Sanechips, CMCC |
| R2-2400934 | 2Rx Non-RedCap XR device access | Apple, Verizon |
| R2-2400935 | 2Rx Non-RedCap XR device access | Apple, Verizon |
| R2-2401454 | 2Rx Non-RedCap XR device access | Apple, Verizon |
| R2-2401501 | Introduction of 2Rx relaxation for XR devices [2Rx_XR_Device] | Huawei, HiSilicon, Telecom Italia, Telia Company, Orange, NTT Docomo, Spark NZ Ltd., CATT |
| R2-2401502 | Introduction of 2Rx relaxation for XR devices [2Rx_XR_Device] | Huawei, HiSilicon, Telecom Italia, Telia Company, Orange, NTT Docomo, Spark NZ Ltd., CATT |
| R2-2401503 | Introduction of 2Rx relaxation for XR devices [2Rx_XR_Device] | Huawei, HiSilicon, Telecom Italia, Telia Company, Orange, NTT Docomo, Spark NZ Ltd., CATT |
| R2-2401504 | RRC CR for UE capability for 2Rx XR devices [2Rx_XR_Device] | Huawei, HiSilicon, Telecom Italia, Telia Company, Orange, NTT Docomo, Spark NZ Ltd., CATT |
| R2-2401507 | Introduction of 2Rx non-RedCap XR UE | Qualcomm Incorporated, BT plc, Ericsson, Nokia, Nokia Shanghai Bell, Meta |
| R2-2401508 | Introduction of 2Rx non-RedCap XR UE | Qualcomm Incorporated, BT plc, Ericsson, Nokia, Nokia Shanghai Bell, Meta |
| R2-2401509 | Introduction of 2Rx non-RedCap XR UE | Qualcomm Incorporated, BT plc, Ericsson, Nokia, Nokia Shanghai Bell, Meta |
| R2-2401510 | Introduction of 2Rx non-RedCap XR UE | Qualcomm Incorporated, BT plc, Ericsson, Nokia, Nokia Shanghai Bell, Meta |
| R2-2401511 | Introduction of 2Rx non-RedCap XR UE | Qualcomm Incorporated, BT plc, Ericsson, Nokia, Nokia Shanghai Bell, Meta |
| R2-2401560 | Introduction of 2Rx XR UE [2Rx_XR_Device] | Qualcomm Incorporated, AT&T, BT Plc, CATT, Ericsson, FutureWei, Huawei, HiSilicon, MediaTek, Meta, Nokia, Nokia Shanghai Bell, NTT Docomo, Samsung, Telecom Italia, T-Mobile USA, Verizon Wireless, ZTE Corporation, Sanechip |
| R2-2401561 | Introduction of 2Rx XR UE [2Rx_XR_Device] | Qualcomm Incorporated, AT&T, BT Plc, CATT, Ericsson, FutureWei, Huawei, HiSilicon, MediaTek, Meta, Nokia, Nokia Shanghai Bell, NTT Docomo, Samsung, Telecom Italia, T-Mobile USA, Verizon Wireless, ZTE Corporation, Sanechip |
| R2-2401562 | Introduction of 2Rx XR UE [2Rx_XR_Device] | Qualcomm Incorporated, AT&T, BT Plc, CATT, Ericsson, FutureWei, Huawei, HiSilicon, MediaTek, Meta, Nokia, Nokia Shanghai Bell, NTT Docomo, Samsung, Telecom Italia, T-Mobile USA, Verizon Wireless, ZTE Corporation, Sanechip |
| R2-2401563 | Introduction of 2Rx XR UE [2Rx_XR_Device] | Qualcomm Incorporated, AT&T, BT Plc, CATT, Ericsson, FutureWei, Huawei, HiSilicon, MediaTek, Meta, Nokia, Nokia Shanghai Bell, NTT Docomo, Samsung, Telecom Italia, T-Mobile USA, Verizon Wireless, ZTE Corporation, Sanechip |
| R2-2401718 | Introduction of TxDiversity for 2Tx capability | OPPO, Huawei, HiSilicon |
| R2-2401719 | Introduction of TxDiversity for 2Tx capability | OPPO, Huawei, HiSilicon |
| R2-2401825 | Introduction of TxDiversity for 2Tx capability | OPPO, Huawei, HiSilicon |
| R2-2401826 | Introduction of TxDiversity for 2Tx capability | OPPO, Huawei, HiSilicon |
| R2-2401959 | Introduction of 2Rx non-RedCap XR UE | Qualcomm Incorporated, BT plc, Ericsson, Nokia, Nokia Shanghai Bell, Meta |
| R2-2401960 | 2Rx Non-RedCap XR device access | Apple, Verizon |
| R2-2401961 | 2Rx Non-RedCap XR device access | Apple, Verizon |
| R2-2401962 | 2Rx Non-RedCap XR device access | Apple, Verizon |
| R2-2401963 | 2Rx Non-RedCap XR device access | Apple Inc., Vodafone |
| R2-2401964 | 2Rx Non-RedCap XR device access | Apple, Verizon, Vodafone |
| R2-2401971 | Introduction of 2Rx non-RedCap XR UE | Qualcomm Incorporated, BT plc, Ericsson, Nokia, Nokia Shanghai Bell, Meta |
| R2-2401972 | Introduction of 2Rx non-RedCap XR UE | Qualcomm Incorporated, BT plc, Ericsson, Nokia, Nokia Shanghai Bell, Meta |
| R2-2401986 | 2Rx XR device access [2Rx_XR_Device] | Apple Inc., Vodafone |
| R2-2401987 | Introduction of 2Rx XR UE [2Rx_XR_Device] | Apple Inc., Vodafone, AT&T |
| R2-2401988 | Introduction of 2Rx XR UE [2Rx_XR_Device] | Apple Inc., Vodafone, AT&T |
| R2-2401989 | Introduction of 2Rx XR UE [2Rx_XR_Device] | Apple Inc., Vodafone, AT&T |
| R2-2402031 | Introduction of TxDiversity for 2Tx capability | OPPO, Huawei, HiSilicon, Samsung |
| R2-2402032 | Introduction of TxDiversity for 2Tx capability | OPPO, Huawei, HiSilicon, Samsung |
| R2-2402037 | Introduction of 2Rx XR UEs [2Rx_XR_Device] | Apple Inc., Vodafone, AT&T |
| R2-2402063 | Introduction of 2Rx XR UE [2Rx_XR_Device] | Apple Inc., Vodafone, AT&T |
| R2-2402064 | Introduction of 2Rx XR UEs [2Rx_XR_Device] | Apple Inc., Vodafone, AT&T |
| R2-2402065 | Introduction of 2Rx XR UEs [2Rx_XR_Device] | Apple Inc., Vodafone, AT&T |
| R2-2402070 | Introduction of 2Rx XR UEs [2Rx_XR_Device] | Apple Inc., Vodafone, AT&T |
| 7.24.2.2 | Other RAN2 TEI-18 | |
| R2-2400004 | Reply LS on emergency cause value for relay (C1-239362; contact: OPPO) | CT1 |
| R2-2400167 | Discussion on redirection to GERAN | vivo |
| R2-2400168 | Correction on redirection to GERAN | vivo |
| R2-2400187 | Beam failure recovery for SDT (RA-SDT and MT-SDT) | Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE, Sanechips |
| R2-2400188 | Introduction of beam failure recovery for SDT in Rel-18 [RA-SDT_BeamFailure] | Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE, Sanechips |
| R2-2400189 | UE capabilities for Beam failure recovery for SDT [RA-SDT_BeamFailure] | Sony |
| R2-2400190 | UE capabilities for Beam failure recovery for SDT [RA-SDT_BeamFailure] | Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE Corporation, Sanechips, Samsung |
| R2-2400200 | Handling SSB failure during SDT Procedure | Samsung Electronics Co., Ltd, ZTE Corporation, Sanechips, Ericsson |
| R2-2400427 | ASN.1 corrections for TEI18 [PosL2RemoteUE] | MediaTek Inc. |
| R2-2400622 | Extension of time domain offset for extended CG-SDT periodicity | NEC Corporation. |
| R2-2400626 | Discussion on open issues for BT-AoA-AoD (B007 and other) | Lenovo |
| R2-2400627 | Correction on support of Bluetooth positioning mode [BT-AoA-AoD] | Lenovo |
| R2-2400645 | Discussion on emergency cause value for SL Relay | OPPO |
| R2-2400646 | Introduction of emergency cause value for SL relay [NR_SL_relay_emergency] | OPPO |
| R2-2400647 | Introduction of emergency cause value for SL relay [NR_SL_relay_emergency] | OPPO |
| R2-2400740 | Setting emergency cause value in L2 U2N relay operation (C1-239362) | Huawei, HiSilicon |
| R2-2400752 | Introduction of Beam Failure for RA-SDT [RA-SDT_BeamFailure] | ZTE Corporation, Sanechips, Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSiliconSamsung |
| R2-2400849 | Introduction of mIAB inter-RAT cell reselection enhancements for 36.331 | Samsung, AT&T, Intel, LG Electronics, Sony |
| R2-2400850 | Introduction of mIAB inter-RAT cell reselection enhancements for 36.304 | Samsung, AT&T, Intel, LG Electronics, Sony |
| R2-2400905 | Failure information in RLF-report for inter-RAT mobility | SHARP Corporation |
| R2-2400930 | Introduction of barring exemption for RedCap UEs with 1Rx branch for emergency calls | Apple, Vodafone, Verizon, TMobile USA, ZTE, Vivo, MediaTek Inc |
| R2-2400931 | Introduction of barring exemption for RedCap UEs with 1Rx branch for emergency calls | Apple, Vodafone, Verizon, TMobile USA, ZTE, Vivo, MediaTek Inc |
| R2-2400932 | Introduction of barring exemption for eRedCap UEs with 1Rx branch for emergency calls | Apple, Vodafone, Verizon, TMobile USA, ZTE, Vivo, MediaTek Inc |
| R2-2400933 | Introduction of barring exemption for eRedCap UEs with 1Rx branch for emergency calls | Apple, Vodafone, Verizon, TMobile USA, ZTE, Vivo, MediaTek Inc |
| R2-2401145 | Introduction of PDCCH CCE Usage for gNB Layer 2 measurement | CMCC, China Unicom, Huawei, ZTE, CATT |
| R2-2401146 | Introduction of PDCCH CCE Usage for gNB Layer 2 measurement | CMCC, China Unicom, Huawei, ZTE, CATT |
| R2-2401233 | Reselection with mIAB cells and CSG cells | LG Electronics Inc, Samsung |
| R2-2401255 | Corrections to Local Cartesian Coordinates [PosLocalCoords] | Qualcomm Incorporated |
| R2-2401257 | [RIL Q033] localOrigin-r18 definition is not in agreement with TS 23.032/29.572 | Qualcomm Incorporated |
| R2-2401315 | Miscellaneous RIL corrections for GNSS LOS/NLOS [GNSS LOS/NLOS] | Ericsson, Vodafone, Spirent |
| R2-2401316 | Miscellaneous RIL corrections for Bluetooth AoA/AoD [BT-AoA-AoD] | Ericsson |
| R2-2401338 | LS to RTCM regarding recent SSR updates [Related to RIL WI GNSS-PCV] | Ericsson |
| R2-2401347 | RedCAP/eRedCAP and Emergency call handling | Vodafone, Apple Inc, Verizon, Deutsche Telekom, BT Plc, TMobile USA, Ericsson |
| R2-2401390 | [H073]Clarification of cell individual offset in reportConfig [CIO_in_ReportConfig] | Ericsson, NTT Docomo, Apple |
| R2-2401392 | [H058]Enhancing SCell A2 event reporting [SCell_A2_Enh] | Ericsson, Huawei, HiSilicon |
| R2-2401458 | ASN.1 corrections for TEI18 [PosL2RemoteUE] | MediaTek Inc. |
| R2-2401474 | Discussion on beam failure recovery for RA-SDT | OPPO |
| R2-2401613 | Miscellaneous RIL corrections for GNSS LOS/NLOS [GNSS LOS/NLOS] | Ericsson |
| R2-2401614 | Miscellaneous RIL corrections for Bluetooth AoA/AoD [BT-AoA-AoD] | Ericsson |
| R2-2401637 | Miscellaneous RIL corrections for Bluetooth AoA/AoD [BT-AoA-AoD] | Ericsson |
| R2-2401642 | Miscellaneous RIL corrections for Bluetooth AoA/AoD [BT-AoA-AoD] | Ericsson |
| R2-2401645 | Introduction of emergency cause value for SL relay [NR_SL_relay_emergency] | OPPO |
| R2-2401845 | [E073][H059]Clarification on cell individual offset in ReportConfig [CIO_in_ReportConfig] | Ericsson, NTT Docomo, Apple, Huawei, HiSilicon |
| R2-2401913 | Correction on support of Bluetooth positioning mode [BT-AoA-AoD] | Lenovo, Ericsson |
| R2-2401917 | Introduction of emergency cause value for SL relay [NR_SL_relay_emergency] | OPPO |
| R2-2401927 | Introduction of beam failure recovery for SDT in Rel-18 [RA-SDT_BeamFailure] | Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE Corporation, Sanechips |
| R2-2401928 | UE capabilities for Beam failure recovery for SDT [RA-SDT_BeamFailure] | Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE Corporation, Sanechips, Samsung |
| R2-2401929 | Introduction of Beam Failure for RA-SDT [RA-SDT_BeamFailure] | ZTE Corporation, Sanechips, Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Samsung |
| R2-2401932 | Correction on redirection to GERAN | vivo |
| R2-2401934 | Introduction of mIAB Inter-RAT cell reselection enhancements for 36.331 [TEI18_MIAB_IRAT] | Samsung, AT&T, Intel, LG Electronics, Sony |
| R2-2401935 | Introduction of mIAB inter-RAT cell reselection enhancements for 36.304 | Samsung, AT&T, Intel, LG Electronics, Sony |
| R2-2401939 | [E073][H059][B013]Clarification on cell individual offset in ReportConfig [CIO_in_ReportConfig] | Ericsson, NTT Docomo, Apple, Huawei, HiSilicon, Lenovo |
| R2-2401941 | Introduction of PDCCH CCE Usage for gNB Layer 2 measurement [L2M_PDCCH_Usage] | CMCC, China Unicom, Huawei, ZTE, CATT, Samsung |
| R2-2401965 | Introduction of mIAB Inter-RAT cell reselection enhancements for 36.306 [TEI18_MIAB_IRAT] | Samsung |
| R2-2401978 | Introduction of PDCCH CCE Usage for gNB Layer 2 measurement [L2M_PDCCH_Usage] | CMCC, China Unicom, Huawei, ZTE, CATT, Samsung, Ericsson |
| R2-2401981 | Introduction of mIAB Inter-RAT cell reselection enhancements for 36.304 [TEI18_MIAB_IRAT] | Samsung, AT&T, Intel, LG Electronics, Sony |
| 7.25.1.1 | Lower MSD capability | |
| R2-2400065 | Reply LS on power class indication in lower MSD capability (R4-2321997; contact: Huawei) | RAN4 |
| R2-2400234 | Left issues on lower MSD capability | OPPO |
| R2-2400722 | Further considerations on lower MSD capability | Huawei, HiSilicon, Ericsson, Xiaomi, ZTE Corporation, Sanechips |
| R2-2400723 | Lower MSD capability for EN-DC | Huawei, HiSilicon, Ericsson |
| R2-2400724 | Lower MSD capability for EN-DC | Huawei, HiSilicon, Ericsson |
| R2-2400725 | Lower MSD capability for EN-DC | Huawei, HiSilicon, Ericsson |
| R2-2400726 | Lower MSD capability for EN-DC | Huawei, HiSilicon, Ericsson |
| R2-2401177 | Lower MSD handling | Nokia, Nokia Shanghai Bell |
| R2-2401944 | Lower MSD capability for EN-DC | Huawei, HiSilicon, Ericsson |
| R2-2401945 | Lower MSD capability for EN-DC | Huawei, HiSilicon, Ericsson |
| R2-2401946 | Lower MSD capability for EN-DC | Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips |
| R2-2401947 | Lower MSD capability for EN-DC | Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips |
| 7.25.1.2 | Intra-band non-collocated NR-CA. EN-DC | |
| R2-2401534 | [H075-H077] Miscellaneous corrections on intra-band non-collocated NR-CA, EN-DC | Huawei, HiSilicon, OPPO |
| R2-2401948 | [H075-H077] Miscellaneous corrections on intra-band non-collocated NR-CA, EN-DC | Huawei, HiSilicon, OPPO |
| 7.25.1.3 | TCI State Switch indication for HST | |
| R2-2400655 | MAC CR for cross RRH TCI state switch indication | Huawei, HiSilicon |
| 7.25.1.4 | FR2 Multi Rx operation | |
| R2-2401287 | RRC RIL list for R18 MultiRx | Apple |
| R2-2401288 | RRC CR addressing MultiRx RIL(s) | Apple |
| 7.25.1.5 | FR2 SCell Enhancements | |
| R2-2401388 | Correction to MAC for FR2 unknown SCell activation enhancements | Ericsson |
| R2-2401389 | Correction to RRC for FR2 unknown SCell activation enhancements | Ericsson |
| 7.25.1.6 | ATG | |
| R2-2400055 | LS on Layer-1/2/3 ATG UE features and koffset mechanism (R4-2321609; contact: CMCC) | RAN4 |
| R2-2400851 | Various corrections on ATG | Samsung |
| R2-2401136 | Correction on Timing Advance Report MAC CE to TS 38.321 for NR R18 ATG | CMCC |
| R2-2401137 | Miscellaneous corrections to TS 38.331 on NR R18 ATG | CMCC |
| R2-2401144 | ATG ASN1 RIL List | CMCC |
| R2-2401214 | Discussion on SUL issues for ATG | China Telecom |
| R2-2401223 | CR on Clarification to SUL issues for ATG | China Telecom |
| R2-2401442 | Discussion on remaining issues of ATG | ZTE Corporation |
| R2-2401804 | LS on Layer-2/3 ATG UE features (R4-2403467; contact: CMCC) | RAN4 |
| R2-2401942 | Correction on Timing Advance Report MAC CE to TS 38.321 for NR R18 ATG | CMCC |
| R2-2401943 | Miscellaneous corrections to NR ATG | CMCC |
| R2-2401956 | Clarification on the eventD1-MeasReportTrigger-r17 for ATG | ZTE Corporation |
| R2-2401980 | Clarification on Timing Advance Report MAC CE for NR ATG | CMCC, Qualcomm |
| 7.25.1.7 | Other | |
| R2-2400032 | LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 (R1-2312668; contact: Qualcomm) | RAN1 |
| R2-2400049 | LS on new per band per BC TxD capability (R4-2317762; contact: Huawei) | RAN4 |
| R2-2400063 | LS on 2Tx-TxD capability and 4Tx-TxD capability (R4-2321983; contact: Samsung) | RAN4 |
| R2-2400235 | Left issues on per-BC-per-band Tx-diversity | OPPO |
| R2-2400259 | Discussion on RAN1 LS in R2-2400032 on inter-frequency configuration in SIB4 with new CSGN for less-than-5MHz | CATT |
| R2-2400430 | Discussion regarding LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 | Qualcomm Incorporated |
| R2-2400431 | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | Qualcomm Incorporated |
| R2-2400432 | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | Qualcomm Incorporated |
| R2-2400433 | [DRAFT] Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 | Qualcomm Incorporated |
| R2-2400463 | Miscellaneous corrections on TS 38.300 for BWP operation without restriction | vivo, Vodafone |
| R2-2400464 | RIL list for BWP_Wor | vivo, Vodafone |
| R2-2400465 | [V990-V992] Miscellaneous corrections on TS 38.331 for BWP operation without restriction | vivo, Vodafone |
| R2-2400466 | [V993] Discussion on NCD-SSB time offset for BWP_Wor | vivo |
| R2-2400467 | Clarification on TxDiversity for 2Tx | vivo, Samsung, Huawei, Hisilicon |
| R2-2400706 | On NR neighbour cells supporting dedicated spectrum less than 5MHz for FR1 | MediaTek Inc. |
| R2-2400714 | Discussion on indicating inter-frequency neighbour cells of less than 5 MHz | Huawei, HiSilicon |
| R2-2400841 | UE capability for Enhanced channel raster | Ericsson |
| R2-2400842 | UE capability for Enhanced channel raster | Ericsson |
| R2-2400867 | Clarification to Tx diversity capabilities | Nokia, Nokia Shanghai Bell |
| R2-2400903 | Introduction of Rel-18 HST FR2 RRM enhancements | Samsung, Qualcomm, Ericsson |
| R2-2401033 | Clarification on the Tx Diversity Capability | ZTE Corporation, Sanechips |
| R2-2401113 | Correction on network RRC signalling for advanced receiver | CATT, China Telecom |
| R2-2401124 | Correction on further measurement gap enhancements | MediaTek Inc. (Rapporteur) |
| R2-2401360 | Support of Enhanced channel raster for (e)RedCap | Ericsson |
| R2-2401483 | [V993] Discussion on NCD-SSB time offset for BWP_Wor | vivo, Guangdong Genius |
| R2-2401506 | Clarification on TxDiversity for 2Tx | Vivo, Samsung, Huawei, HiSilicon |
| R2-2401533 | RIL list for advanced receiver | CATT, China Telecom |
| R2-2401565 | Introduction of Rel-18 HST FR2 RRM enhancements | Samsung, Qualcomm, Ericsson |
| R2-2401603 | UE capability for Enhanced channel raster | Ericsson |
| R2-2401604 | UE capability for Enhanced channel raster | Ericsson |
| R2-2401706 | LS on NCD-SSB time offset for non-RedCap UEs in TDD (R1-2401743; contact: Vodafone) | RAN1 |
| R2-2401802 | Reply LS on RRC network assistant signalling for advanced receiver on MU-MIMO scenario (R4-2403086; contact: China Telecom, CATT) | RAN4 |
| R2-2401818 | Reply to LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 (R4-2403852; contact: Huawei) | RAN4 |
| R2-2401819 | LS on applicable release of per FS TxD capability (R4-2403857; contact: OPPO) | RAN4 |
| R2-2401856 | Clarification on TxDiversity for 2Tx | Vivo, Samsung, Huawei, HiSilicon |
| R2-2401857 | Miscellaneous corrections on TS 38.331 for BWP operation without restriction | vivo, Vodafone |
| R2-2401858 | LS on NCD-SSB time offset for non-(e)RedCap UEs in TDD | RAN2 |
| R2-2401859 | RIL list for BWP_Wor | vivo, Vodafone |
| R2-2401860 | Correction on network RRC signalling for advanced receiver | CATT, China Telecom |
| R2-2401861 | Correction on further measurement gap enhancements | MediaTek Inc. (Rapporteur) |
| R2-2401862 | [RIL list] | MediaTek Inc. |
| R2-2401885 | Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 | RAN2 |
| R2-2401949 | Miscellaneous corrections on TS 38.300 for BWP operation without restriction | vivo, Vodafone |
| R2-2402028 | UE capability for Enhanced channel raster | Ericsson |
| R2-2402029 | UE capability for Enhanced channel raster | Ericsson |
| R2-2402045 | LS on NCD-SSB time offset for non-(e)RedCap UEs in TDD | RAN2 |
| 7.25.2 | RAN1 led items | |
| R2-2400064 | LS on Rel-18 Tx switching enhancement (R4-2321986; contact: Huawei) | RAN4 |
| R2-2400236 | Left Issues on Tx-Switching | OPPO |
| R2-2400738 | RRC RIL issue list for Rel-18 Multi-carrier enhancements | Huawei, HiSilicon |
| R2-2400739 | Rapp RRC CR for Rel-18 Multi-carrier enhancements | Huawei, HiSilicon, NTT DOCOMO INC., Intel, Qualcomm |
| R2-2400741 | On ambiguity issue of switching period (LS R4-2321986) | Huawei, HiSilicon, OPPO, Apple, Ericsson, NTT DOCOMO INC. |
| R2-2401178 | [N041] Multicarrier DCI Scheduling | Nokia, Nokia Shanghai Bell |
| R2-2401216 | Discussion on UL Tx switching for parallel switching on four bands | MediaTek Inc. |
| R2-2401217 | [DRAFT] Reply LS on resolving Tx switching ambiguity issue | MediaTek Inc. |
| R2-2401225 | [DRAFT] Reply LS on Rel-18 UL Tx switching for parallel switching on four bands | MediaTek Inc. |
| R2-2401331 | Discussion on change of MAC spec for Multi-carrier enhancements | NTT DOCOMO, INC. |
| R2-2401334 | Introduction of Multi-carrier enhancements | NTT DOCOMO INC. |
| R2-2401441 | Discussion on remaining issues of Rel-18 UL Tx switching | ZTE Corporation |
| R2-2401572 | Correction to 38.300 for multi-cell scheduling | NTT DOCOMO, INC. |
| R2-2401577 | RRC CR for Rel-18 Multi-carrier enhancements | Huawei, HiSilicon, NTT DOCOMO INC., Intel, Qualcomm, Nokia, Nokia Shanghai Bell |
| R2-2401578 | UE capability for Rel-18 Multi-carrier enhancements | Huawei, HiSilicon |
| R2-2401579 | UE capability for Rel-18 Multi-carrier enhancements | Huawei, HiSilicon |
| R2-2401703 | LS on TS38.300 TP for Multi-cell scheduling in Rel-18 (R1-2401716; contact: NTT DOCOMO) | RAN1 |
| R2-2401710 | Reply LS on UL Tx switching (R1-2401776; contact: NTT DOCOMO) | RAN1 |
| R2-2401776 | MC Enh RIL list | Huawei |
| R2-2401810 | Reply LS on UL Tx switching (R4-2403657; contact: vivo) | RAN4 |
| R2-2401854 | Introduction of Multi-carrier enhancements | NTT DOCOMO INC. |
| R2-2401969 | Reply LS on Rel-18 UL Tx switching for parallel switching on four bands | RAN2 |
| R2-2401970 | Introduction of Multi-carrier enhancements | NTT DOCOMO INC. |
| R2-2402049 | Correction to 38.300 for multi-cell scheduling | NTT DOCOMO, INC. |
| R2-2402061 | Introduction of Multi-carrier enhancements | NTT DOCOMO INC. |
| 7.25.3 | Other | |
| R2-2400089 | LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE (S5-237941; contact: Samsung) | SA5 |
| R2-2400217 | LS on Trace functionality extension in N3IWF for non-3GPP access scenarios (S5-241051; contact: Nokia) | SA5 |
| R2-2400656 | Discussion on the issues in the LS S5-237941 | Huawei, HiSilicon |
| R2-2400657 | Draft reply LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE | Huawei, HiSilicon |
| R2-2400745 | MPS setup | Ericsson |
| R2-2400774 | [Draft] Reply LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE | Samsung |
| R2-2400775 | Clarification on packet loss rate with delay threshold | Samsung |
| R2-2401097 | Discussion on the LS from SA5 about Packet Uu Loss Rate with delay threshold | CATT |
| R2-2401676 | Reply LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE | RAN2 |
| R2-2401679 | Clarification on packet loss rate with delay threshold | Samsung |
| 8.1 | Session on LTE V2X and NR SL | |
| R2-2401541 | Report from session on LTE V2X and NR SL | Vice Chairman (Samsung) |
| 8.2 | Session on NR MIMO evolution and Multi-SIM | |
| R2-2401542 | Report from session on NR MIMO evolution and Multi-SIM | Vice Chairman (CATT) |
| 8.3 | Session on NR NTN and IoT NTN | |
| R2-2401543 | Report from Break-Out Session on NR NTN and IoT NTN | Session chair (ZTE) |
| 8.4 | Session on positioning and sidelink relay | |
| R2-2401544 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
| 8.5 | Session on Mobility Enh and Mobile IAB | |
| R2-2401545 | Report from session on Mobility Enh and Mobile IAB | Session chair (MediaTek) |
| 8.6 | Session on MBS and QoE | |
| R2-2401546 | Report from session on MBS and QoE | Session chair (Huawei) |
| 8.7 | Session on SON/MDT and NCR | |
| R2-2401547 | Report from SON/MDT and NCR session | Session chair (Apple) |
| 8.8 | Session on IDC | |
| R2-2401548 | Report from IDC breakout session | Session chair (Intel) |
| 8.9 | Session on maintenance and eRedCap | |
| R2-2401549 | Report from maintenance and eRedCap breakout session | Session chair (Ericsson) |
| 8.10 | Session on further NR coverage enhancements | |
| R2-2401550 | Report from Further NR coverage enhancements session | Session chair (ZTE) |